Hardware: Not so old computer YunoHost version: 4.1.6 I have access to my server : Through SSH (both on local network and from internet) | through the webadmin (on local network only) | direct access via keyboard / screen is also working and is an option if needed Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : not sure If yes, please explain:
I first installed and configured the server via a wifi connection, but now it is through ethernet (I finally sorted out the /etc/network/interfaces as my linux knowledge dates 10 years back)
I use a DuckDNS domain and I think the first time I tried to access the server via web it worked (when the server was still through wifi); now in DuckDNS I can see both IPv4 and IPv6 reflect my ISP box, but I can’t access the server via http or https.
Also when the server was still on Wifi I tried to force a Letsencrypt certificate (–no-checks), but in the webadmin it still shows the self-signed certificate anyway
Description of my issue
Hello, despite my best efforts I can’t get to fix the access to my server via internet (“from outside”)
I redirected all ports to my server in my ISP box (BBOX v3+ from belgian provider Proximus). They are redirected to the local server’s IP (which I defined to be static in the DHCP setting).
I don’t know what I am doing or did wrong, so any help would be appreciated!
I found the culprit!
For my Belgian friends that may one day face the same issue: The forwarding of ports 23, 80 an 443 are not allowed by default. Nothing in the port mapping interface says it but you can find the info at the bottom of this page:
This can be allowed by lowering the security (access via MyProximus>Parameters)
Then a reboot of the modem/router (unplug 5 seconds).
I have now most things working, except that no ports are accessible via ipv6, which prevents me generating a Letsencrypt certificate, but I can live with it for now.
Not sure what the diagnosis say about this, but it should be fine as long as you do not add the AAAA record on your DNS (otherwise Let’s Encrypt will prioritize AAAA for the acme-challenge and ignore the A record)