Poort 443 van computer lijkt niet toegankelijk

AI-generated summary

Rizwan_Anwar encountered issues installing Discourse due to port 443 being inaccessible, initially suspecting DNS or NAT-related problems Rizwan_Anwar. After rebuilding the app failed, supermathie suggested it might be a warning and noted potential NAT interference. Benjamin_D identified Apache as the likely culprit, occupying port 80 (and possibly 443), which conflicted with Discourse’s needs. Rizwan confirmed Apache was running and followed the cloud install guide, but kept seeing the Apache default page instead of Discourse Rizwan_Anwar. Benjamin_D advised stopping and disabling Apache via sudo systemctl stop apache2 && sudo systemctl disable apache2 or even uninstalling it Benjamin_D. After stopping Apache, Rizwan initially saw a “site can’t be reached” error Rizwan_Anwar, but after rebuilding the app, Discourse loaded successfully Rizwan_Anwar. Stephen reinforced that Apache is unnecessary and must remain disabled to avoid port conflicts on reboot. Rizwan later reported not receiving activation emails — Stephen clarified this is unrelated and directed him to email troubleshooting topics Stephen. When asked if Nginx was required, Benjamin_D and Stephen confirmed that a standard Discourse install includes Nginx inside the container; no external web server is needed. The core issue was resolved by removing Apache’s port conflict, allowing Discourse to bind to ports 80 and 443.

Found similar issues but none of them worked for me and my DNS IP is the same as machine public IP where I am trying to install Discourse, still getting this error.

It’s just a warning. If you rebuild the container, does it work?

You also might not be able to access the public IP from the computer itself since (given the hostname) it looks like it’s a NATted IP.

when I run ./laucher rebuild app. It failed to rebuild. Also could please tell me whats NATted IP and how can I solve it.

Apache is using the ports isn’t it?

Apache is using port 80 i guess i dont know much about it. I was just following these steps discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

Can this be the problem it says port 443 is closed.

If you have no use for it (might be there by default) you should remove it and then be able to follow the usual steps in the link

Won’t help for sure :sweat_smile:

I have successfully installed discourse but when i am visiting hostname it shows me Apache page instead of Discourse. Any idea what could be going wrong?

I have successfully installed discourse but when i am visiting hostname it shows me Apache page instead of Discourse. Any idea what could be going wrong?

I suggest something like sudo systemctl stop apache2 and sudo systemctl disable apache2 , or even sudo apt remove apache2

If I am stoping apache an then visiting hostname it throws an error this site can’t be reach.

was it with apache down ? (because i’m not sure it could easily be done with apache holding the 80 port)

i have install apache and edit apache conf to Listen 80 Listen 443 and then restart it and ran ./launcher rebuild app and it installed discourse.

Discourse doesn’t require Apache. Disable or uninstall it, then reboot. At that point Discourse will have access to the necessary ports.

Thanks, man. I stop apache and ran ./launcher rebuild app and now i can see discourse on my hostname. :slight_smile:

Make sure Apache is disabled or uninstalled, otherwise the next time your server is rebooted Discourse will be blocked from accessing the port again.

okay and I am not receiving Activation email I have checked spams also.

Ok, that not related to the above. There are topics dedicated to troubleshooting email.

Do i have to install ngnix?