User CorruptBlu encountered an error when setting up Discourse with a .tk domain (speedydev.tk), receiving warnings that ports 80 and 443 were unreachable despite firewall rules allowing them. supermathie advised verifying the domain resolves to the correct server IP (158.101.14.131), which CorruptBlu confirmed. Further troubleshooting included checking if the IP is directly assigned to the VM or NAT’d by Oracle Cloud, and testing external connectivity via a simple server supermathie. CorruptBlu noted the domain worked fine with zapto.org but not .tk, suspecting Freenom domains. After rebuilding the container with ./launcher rebuild appsupermathie, CorruptBlu confirmed the issue persisted until Mevo pointed out even the direct IP was unreachable, suggesting a deeper network or service issue. Eventually, CorruptBlu concluded it might be specific to Freenom domains. After re-adding the .tk domain and waiting, CorruptBlu reported it began working, implying DNS or service propagation delay was the root cause. supermathie had earlier suggested testing the domain even if it resolved correctly — advice that ultimately helped resolve the issue.
When I change the domain to speedydev.tk, it keeps showing this error:
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: speedydev.tk.
WARNING: Connection to http://speedydev.tk (port 80) also fails.
This suggests that speedydev.tk resolves to some IP address that does not reach this
machine where you are installing discourse.
The first thing to do is confirm that speedydev.tk resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.
If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.
This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type
./launcher rebuild app
But in the firewall, ports 80 and 443 are open. What do I do?
If you’ve already done that, have you tried running a simple server listening on port 80 or 443 and seeing if you can connect to it from outside?
Is that IP address assigned to an interface on the VM, or is it translated by a service within Oracle Cloud? If it’s not assigned to an interface, the VM itself may not be able to talk to that IP in which case the test failed incorrectly and you can ignore it.
It worked perfectly fine when I used speedydev.zapto.org as the domain and I was able to connect to it with no problems, but when I changed it to speedydev.tk it no longer works.
Based on the guide for hosting Discourse on Oracle, the Public IP which I said I pointed the domain to, is the IP which is used for the forum.
Currently, if you enter directly the IP in a browser, you get the same error. So, doesn’t seem linked to the domain (which seem to correctly point to this IP address).
A PNG to the IP doesn’t work. Seems nothing is answering at this ip right now.
Ok, it seems like it’s only a problem with domains from Freenom. If I use domains from other places it works fine. Guess I’m back to searching for free domains.