Is It DNS this time or code-server?
Issue: when connecting to the CNAME record I assigned for my code-server within my home internet I am left with the white screen after sign in each time for both the windows and Linux OS's and when using Firefox and Vivaldi between the 2 OS's.
In both browsers I reach the white screen and in both if I wait long enough I load into the code-server just in time to recover a pop-up to reload the page and the process starts back over.
What is extremely odd is when I try the CNAME record when on public wifi or any other network; the website loads directly even when I used my cell home as a hotspot and the same desktop machine. Beyond the core dilemma and the following explanation of my core home setup what is information might be helpful to get assistance troubleshooting? 1. Raspberry pi 4 running Adguard home connected to router 2. Headless Lenovo 64 bit mini PC running debian with docker that runs both Nginx Proxy Manager(npm) and coder/code-server (not Linux server community edition) both repulled latest image as of 12/14 3. Dual boot windows and debian desktop machine. NPM setup for this points to the local docker network on the same bridge network on the default port and I have the website and block common exploits turned on with let'sencrypt proved ssl certs.
What is extremely odd is when I try the CNAME record when on public wifi or any other network; the website loads directly even when I used my cell home as a hotspot and the same desktop machine. Beyond the core dilemma and the following explanation of my core home setup what is information might be helpful to get assistance troubleshooting? 1. Raspberry pi 4 running Adguard home connected to router 2. Headless Lenovo 64 bit mini PC running debian with docker that runs both Nginx Proxy Manager(npm) and coder/code-server (not Linux server community edition) both repulled latest image as of 12/14 3. Dual boot windows and debian desktop machine. NPM setup for this points to the local docker network on the same bridge network on the default port and I have the website and block common exploits turned on with let'sencrypt proved ssl certs.
2 Replies
It might be down to your router blocking you since you have a hairpin nat in that case. As in: You connect to the internet, but come straight back to your selfhosted environment. Firewalls don't like that.
Check how to enable hairpin NAT in your router and it should work.
Thank you; I had considered the DNS routing and was using dig to verify the route was being returned correctly but I hadn't thought about the NAT configuration