Natsu1 installed Discourse on Ubuntu 18.04 via Hyper-V and configured a static IP with port forwarding for port 443, pointing their domain forum.blueskull.win to it. The installation completed successfully, and ./launcher start app confirms Discourse is running, but they cannot access it via the domain. They question whether 0.0.0.0:443 should instead reflect their internal IP. pfaffman explains that Discourse requires a domain name (not just an IP) and public accessibility for Let’s Encrypt to function — or manual configuration to disable it. Natsu1 confirms they have a domain. pfaffman advises ensuring ports 80 and 443 are properly forwarded and suggests running ./discourse-setup, which tests external connectivity (though it may fail if a reverse proxy is present). Natsu1 confirms they ran ./discourse-setup successfully. pfaffman suspects DNS mismatches between client, router, host OS, and VM layers — a complex troubleshooting task — and recommends using a cloud provider like DigitalOcean for simplicity.
The Ubuntu server has a static ip given by my router + port forward port 443 from there and pointed my domain to is.The instillation worked if i try to call the command “./launcher start app” it says that discourse is running correctly. But i cannot access it on my domain. It does say under ports : 0.0.0.0:443 should this be my internal ip of the machine?
It needs a domain name, not an ip. It also needs to be publicly accessible for let’s encrypt to work, and requires extra steps to disable let’s encrypt.
Perhaps your server machine uses a different dns than your client. Getting that stuff working between all the layers of your router, the server os, the visualized vm and so on is tricky. It’s not likely that you’ll get that level of troubleshooting here.
That’s why it’s easier to spend $5 or $10 /month to digital ocean.