The latest upgrade required rebuilding the app in launcher, but it failed. First it complained about having the adplugin as a separate install, so I removed that. Looks like then it failed trying to migrate the secondsite database: 2025-08-21 06:44:42.493 UTC [867] discourse@discourse_nu ERROR:…

[이미지] MikeNolan: in the nginx config files within the container, it checks to see if the URL is not for the first site and changes it to that. I commented out that code–again There have been big changes in how the nginx config is handled. Do you have a multisite setup with no reverse proxy?

Cause The migration tries to upgrade the “vector” extension. The PostgreSQL user running the migration (e.g. discourse) must be the owner of the extension, but it’s owned by a different user (often postgres). Solution Connect to your database as the owner Run the update as the owner Checkout the…

That fixed it. However, the problem with nginx and secondsites that I reported over a year ago is still there, in the nginx config files within the container, it checks to see if the URL is not for the first site and changes it to that. I commented out that code–again.

Well, it’s been nearly 2 years since I’ve looked at nginx much, but this problem existed when I first moved over to Discourse 2 years ago, so it is not new. Here’s an excerpt from the nginx.conf file: server { server_name huskerlist.tssi.com; root /var/www/html; allow 162.210…

Apparently every time it set up a new container (such as during a reboot) it rewrites the /etc/nginx/conf.d/outlets/server/20-https.conf file, and these lines cause a redirect to the default discourse system: if ($https_host != huskerlist.tssi.com ) { rewrite (.$) https://huskerlist.tssi.com } I…

[이미지] MikeNolan: Apparently every time it set up a new container (such as during a reboot) it rewrites the /etc/nginx/conf.d/outlets/server/20-https.conf file That’s right. Are you editing that file inside of the container? Building a new container builds a new container. It’s not rewriting …

So, essentially what you’re saying is that the ‘secondsite’ method for hosting two independent forums on one server is broken and not on the list of things to fix. so you could either delete it or find a way to make it also check for your other hostnames. Deleting it in the container is what I’v…

Thinking about it briefly, fixing the ssl template is somewhat challenging. The current logic says: If the site isn’t A, make it A. Introducing a secondsite complicates things, because if it isn’t A and it isn’t B, it also isn’t clear that changing it to either A or B is the right thing to do. (T…

[이미지] MikeNolan: So, essentially what you’re saying is that the ‘secondsite’ method for hosting two independent forums on one server is broken and not on the list of things to fix. It was never on the list of things to support. The recommended was was always to use a reverse proxy. I contriv…

Since I’m using nginx with proxy_pass to pass traffic to the container for two different FQDNs, am I correct that mean I’m using the reverse proxy method for multisite?

Yes. I forgot about that one! Have nginx proxy do the https and remove the ssl and let’s encrypt templates from your yml file and rebuild.

2025-08-21 최신 릴리스로 업그레이드 실패

지원 자체 호스팅

pfaffman (Jay Pfaffman) 9월 13, 2025, 10:28오전 12

네. 그거 잊어버렸네요!

nginx 프록시로 https를 처리하도록 하고, yml 파일에서 ssl 및 let’s encrypt 템플릿을 제거한 뒤 다시 빌드하세요.

글		댓글	조회수
Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy Sysadmins how-to , domains	24	4836	8월 27, 2026
The upgrade saga continues Self-hosting unsupported-install , hosting	4	185	9월 17, 2025
Add an offline page to display when Discourse is rebuilding or starting up Sysadmins configuring , how-to , advanced-setup	140	247009	2월 3, 2026
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	139120	6월 30, 2026
More than one site as different container running on the same do server Self-hosting	3	859	12월 24, 2019

2025-08-21 최신 릴리스로 업그레이드 실패

Related topics