Hi, I’m currently trying to update our DEV-Instance to the most recent Beta 7, coming from Beta 2. It’s running on the default `tests-passed’ branch. My issue is that rebuilding the container ends in a connectivity issue (I guess) with github: I, [2025-07-28T12:35:19.480463 #1] INFO -- : Replac…

Ooof, I figured it out finally. The issue was indeed with docker and the host network, not discourse. Hetzner, if you run a vSwitch with a public Subnet, requires the MTU to be set to 1400 instead of 1500. I did change that at some point, but apparently that change got reverted at some point. So I …

Do you have many plugins listed in your app.yml file? It might be worthwhile to comment them all out and see if things work, and if so you can begin to comment then back in again. Edit: be sure to take a safe copy of the yml file first! And as always, make a backup and download it before starting …

We don’t use many Plugins. I also already removed the ones that got implemented into the core as per the changelogs. Only these are set currently: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-translator.git …

It feels like a provider issue, or perhaps a kernel issue. But I don’t have familiarity with a dev install.

It’s hosted at Hetzner in Germany, there’s also nothing special about the kernel, just default debian 11 at Kernel 5.10.237-1. DEV-Instance only refers to it being our testing instance to try things like updates/upgrades before doing them on our actual production setup to make sure it doesn’t break…

Ah right. If it’s based on the usual container, and it’s getting connectivity trouble, I think that’s not a Discourse problem. Your kernel is very old. I’m running Ubuntu 24.04 with 6.8.0-53

The Kernel was built May 2025 and is the current one for Debian 11 which is still fully supported. 2 Months isn’t really ‘very old’. But, to rule this out, I upgraded the system to Debian 12 and the most recent mainline Kernel 6.10 (again, not old, this is the most recent debian 12 kernel without r…

That’s very odd. Well done for checking out the kernel - there have been kernel-version incompatibilities but evidently this is not that. You can get a command line inside the container and perhaps try some network operations (wget or curl) but I’m not sure what it might prove. I don’t have any ot…

I’ve found that the errors point towards Git configs that might need changed - but I’m not sure where I would change those since it’s all happening within the container while rebuilding. Changing those on the host itself didn’t really do anything. So changes like git config http.postBuffer 52428800…

Just possibly you can put some command specs in your app.yml file - see [immagine] Install plugins on a self-hosted site # Unset access - git config --global --unset core.sshCommand

I’ve tried that now and no change sadly. Not sure if the command is run before it’s trying to pull/build the actual container. It would have to run right when starting to (re)build. I’d expect those hooks to run after pulling/building the site at /var/www/discourse , which will not finish for me. I…

Problemi nell'aggiornamento/ricompilazione a Beta7

Supporto Installazione

Ed_S (Ed S) 30 Luglio 2025, 3:44pm 10

Forse potresti inserire alcune specifiche di comando nel tuo file app.yml, vedi

Argomento		Risposte	Visualizzazioni
HELP: Discourse Update broke app -- fails to rebuild Self-hosting	14	2098	Gennaio 10, 2023
Error upgrading Self-hosting	12	1671	Ottobre 20, 2016
Can't build container, no clear errors Self-hosting	2	2231	Marzo 2, 2022
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2186	Novembre 26, 2021
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2131	Dicembre 28, 2023

Problemi nell'aggiornamento/ricompilazione a Beta7

Argomenti correlati