When i create a new website and add new web contect it constantly sends me to my internal firewall config page from inside my network. Outside of my home network, i have no issues. when i do ispconfig_update.sh --force it restores that ability. I cannot figure this out, it does this on every new website installed.
So from inside your local LAN you can not access the website? But website does work from the public Internet? If this is the case, my guess is the website URL resolves from name service to the public IP address. You can use this method on your workstation to access that website with the IP-address it has on local LAN: https://www.faqforge.com/windows/how-to-access-a-namebased-website-without-a-dns-record/
That is exactly what is happening. I did try this fix and it did not work. Just for ..... and giggles I added it again and did a nslookup from my surface pro and it still went to my firewall page. I double checked via my cell phone off my wireless and it went to my default apache2 page. My firewall is Ubuiqiti UDM Pro. Just to give more clarity. I also did a ispconfig_update.sh --force with no luck Server's public ip(s) (x.x.x.x) not found in A/AAAA records for jedimud.jedimud.com: 127.0.1.1
I'm not sure the hosts file can be modified on a Surface Pro, but anyway what nslookup shows is not affected by changes in hosts file. Is the firewall between the workstation where you sit at to modify the hosts file and the web server?