I just updated using ./launcher rebuild app and now the website can’t be reached. There were no errors during the Postgres upgrade or the rebuild. Here’s the output from discourse doctor. DISCOURSE DOCTOR Tue Feb 4 10:56:05 PM UTC 2025 OS: Linux redacted 6.8.0-52-generic #53-Ubuntu SMP PREEMPT_DYNA…

Seems like it was caused by this: [afbeelding] Setup Let’s Encrypt + non-www > www Sysadmins I finally made it work, and thought to put everything together in case someone needs it. This info is assembled from different topics on this forum. Thanks to @brahn a…

Have you tried rebuilding in the last 2 hours or so? We did have an issue for a bit, but it’s now been resolved [afbeelding] Site offline after rebuild (4th Feb 2025) Support Sorry for the disruption everyone! The fix is now live, so running another ./lau…

Yes, rebuilt twice within the last hour

[afbeelding] Thomas Reintjes: now the website can’t be reached What error are you seeing when trying to access the site?

“Safari can’t connect to the server”

On your server, can you try running cd /var/discourse git rev-parse HEAD It should say # git rev-parse HEAD efd6bc8ccbd9057c04d909ff48ecf8b704cae3ff

Is there anything ‘unusual’ about your installation? Anywhere that you’ve deviated from the standard install ? The issue you’re describing sounds a lot like the one in the topic I linked. But if you’re seeing the efd6bc8... for the discourse_docker version, then you should have the fix :thinking:

Nothing I can think of, except I have /var/discourse mounted from a disk in fstab. But it’s been running like that for years. Well, thanks for your help. Let me know if anything else comes to mind.

To check whether the same issue is affecting you, you could do something like ./launcher enter app cat /etc/nginx/conf.d/discourse.conf Somewhere in that file should be listen 443 ssl; If it’s missing, then that’s the same symptom as the other topic. If it’s present… then I’m afraid we have som…

Kan webserver niet bereiken na update naar 3.4

Ondersteuning

david (David Taylor) 4 februari 2025 om 23:27 2

Have you tried rebuilding in the last 2 hours or so? We did have an issue for a bit, but it’s now been resolved

Topic		Antwoorden	Weergaven
Site inaccessible after upgrading from 3.4.0 to 3.4.1 Support docker , docker-manager	7	287	8 april 2025
Discourse rebuild fails with port 443 in use Support unsupported-install	11	2997	10 maart 2018
After rebuild, site won't load Self-hosting	13	2199	23 april 2018
Forum down, troubleshooting help needed Self-hosting	18	627	9 augustus 2023
Site offline after rebuild (4th Feb 2025) Support	16	426	6 februari 2025

Kan webserver niet bereiken na update naar 3.4

Gerelateerde topics