I tried my first-time installation of Discourse today. I did move forward to the typical page of “Discourse successful installation”. I did not click “register” button to finish the 14-steps initial configuration. Instead, i opened container/app/yml and change the port from 80 to 8080 (also 443 to …

Why would you change the port? Connecting to discourse on non-standard ports isn’t supported. HTTP means port 80. HTTPS means port 443. To get it back to normal, restore the ports to their supported values.

Thank you Stephen for your reply. I already have installed a Wordpress website on the same server with the main domain www.abc.com . I stoped Nignx and Apache temporarily in order to have Discourse intalled. After the Discourse installation we need to restart Nignx and Apache sevices. That is why I …

You should really be following this guide: [Bild] Run other websites on the same machine as Discourse Self-Hosting If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker cont…

Forum.abc.com nach Port-Änderung zu Container/App/YML nicht mehr erreichbar

Produktunterstützung Installation

itsbhanusharma (Bhanu Sharma) 14. Mai 2020 um 07:52 4

Du solltest diesem Leitfaden wirklich folgen:

Thema		Antworten	Aufrufe
Can't get Discourse to work on different ports Self-hosting	2	1663	9. März 2021
Install Discourse, change docker port 80 Self-hosting unsupported-install , docker	14	15233	11. März 2024
I see Discourse by port number but i couldn't see it to subdomain. (:3001) Self-hosting unsupported-install	7	714	6. Januar 2021
Port already in use, what to do? Self-hosting	26	19999	6. März 2020
What adjustments are needed when discourse uses a non-443 port? Product Support email , bug	10	298	20. November 2025

Forum.abc.com nach Port-Änderung zu Container/App/YML nicht mehr erreichbar

Verwandte Themen