I’m self-hosted and have 3 of the plugins that were recently moved to core. My upgrade steps: Edited containers/app.yml and removed the lines for the 3 plugins (data-explorer, solved, assign) cd /var/discourse sudo ./launcher rebuild app The rebuild takes the usual 5 minutes and seems to complete normally. However, when I attempt to connect to the site, I get no response. The last few lines in /var/discourse/shared/standalone/log/rails/production.log are: Booted Rails 8.0.3 application in production environment Running in ruby 3.3.8 (2025-04-09 revision b200bad6cd) [x86_64-linux] See LICENSE and the LGPL-3.0 for licensing details. Upgrade to Sidekiq Pro for more features and support: ``https://sidekiq.org Sidekiq 7.3.9 connecting to Redis with options {:size=>5, :pool_name=>“default”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} Sidekiq 7.3.9 connecting to Redis with options {:size=>10, :pool_name=>“internal”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} Sidekiq 7.3.9 connecting to Redis with options {:size=>10, :pool_name=>“internal”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} Sidekiq 7.3.9 connecting to Redis with options {:size=>10, :pool_name=>“internal”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} Sidekiq 7.3.9 connecting to Redis with options {:size=>10, :pool_name=>“internal”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} Sidekiq 7.3.9 connecting to Redis with options {:size=>10, :pool_name=>“internal”, :host=>“localhost”, :port=>6379, :db=>1, :url=>nil} The last few lines in /var/discourse/shared/standalone/log/rails/unicorn.stderr.log are: /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/message_bus-4.4.1/lib/message_bus/backends/redis.rb:291:in global_subscribe' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/message_bus-4.4.1/lib/message_bus.rb:769:in global_subscribe_thread’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/message_bus-4.4.1/lib/message_bus.rb:740:in `block in new_subscriber_thread’ unknown OID 23281: failed to recognize type of ‘embeddings’. It will be treated as String. I also tried rebuilding a 2nd time and its still not working. Any idea what’s going on?

[image] xyzzy: , I get no response. So the request times out?

[image] pfaffman: So the request times out? The server refuses the connection. It seems to take about 2 seconds for the connection to be refused in both browsers I’ve tried. And nothing new shows up in production.log.

I’d look at two things is the server process running and listening is your browser trying to contact the correct server Check that your forum URL’s domain name does resolve, from your own PC, to the IP address of your server. Double-check. Perhaps try, on your server ping -c1 DOMAINNAME netstat -l | egrep http lsof -u root | egrep LISTEN

You can try docker logs app The last person I helped had a bogus value for his letsencrypt email address. It sounds like nginx isn’t starting up for some reason. The most common reason is that the certs are broken.

Failed upgrade from 3.5.0.beta8-dev to 3.6.0.beta1

Product Support Self-hosting

xyzzy October 13, 2025, 8:32pm 4

Any ideas what’s going on? Any suggestions for additional debugging steps?

Topic		Replies	Views
Redis Error after upgrade Self-hosting	13	1894	June 3, 2020
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	3240	May 11, 2020
Sidekiq heartbeat test failed, restarting Self-hosting	11	2317	January 12, 2020
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	8186	October 2, 2015
"Sidekiq is not running" Self-hosting	6	3191	February 7, 2016

Failed upgrade from 3.5.0.beta8-dev to 3.6.0.beta1

Related topics