I’ve got the upgrade mostly working. There are two Discourse communities on my server. Inbound email is working on the secondsite community but not on the first site, looking at the logs it shows incoming email is being picked up by the SMTP server but there’s nothing in the discourse email logs to show it was even received much less processed or rejected. I don’t see any settings differences between these two communities that would cause this, and I’m not sure where else to look for clues about what to do to fix it.

Looks like rebooting the server (again) may have fixed it.

Looks like rebooting the server (again) may have fixed it. However, restarting the server built a new container from the image, so the nginx issue is back. Can anyone tell me why this code exists in the nginx config files for a Discourse container: in outlets/server/20-https.conf: if ($http_host != huskerlist.tssi.com) { rewrite (.*) https://huskerlist.tssi.com$1 permanent; IMHO, either this code shouldn’t be there or it should also check $http_host against the secondsite FQDN, etc.

[image] MikeNolan: There are two Discourse communities on my server. How? Are you using a reverse proxy and have multiple containers running?

I’ve moved this topic to #installation:hosting since it appears to be about tinkering with a self-hosted Discourse setup. I also added #unsupported-install because it clearly involves a setup that does not follow the official install guide.

The upgrade saga continues

Product Support Self-hosting

pfaffman (Jay Pfaffman) August 23, 2025, 11:27pm 4

How? Are you using a reverse proxy and have multiple containers running?

Topic		Replies	Views
Upgrade to latest release failed 8/21/25 Self-hosting	11	486	September 13, 2025
Upgrading failing with: The "before-server" Nginx outlet is missing... discourse_docker is not compatible with the chosen Discourse version Product Support	7	342	July 12, 2025
Http shows nginx page Self-hosting	6	395	May 10, 2024
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4407	September 20, 2022
Unable to access after installation - HTTP Self-hosting	18	4396	May 10, 2017

The upgrade saga continues

Related topics