The upgrade saga continues

Product Support Self-hosting
,

AI-generated summary

The discussion, titled “The upgrade saga continues,” revolves around issues with a self-hosted Discourse setup involving two communities on the same server. MikeNolan reports that inbound email works on the second site but not the first, despite the SMTP server picking up the emails—no logs indicate processing or rejection. After rebooting the server, the issue seemed resolved temporarily, but a new container was created, reintroducing an nginx problem. MikeNolan questions the nginx configuration in 20-https.conf, which redirects traffic based on the hostname huskerlist.tssi.com, suggesting it should also account for the second site’s FQDN. pfaffman asks for clarification on how two Discourse communities are hosted, and tobiaseigen moved the topic to the hosting section and tagged it as unsupported due to non-standard installation practices.

1

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.

2

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

3

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.

4

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

5

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.