I just tried the new official install method on hetzner and loved the streamlined experience, and adorable ascii art in the setup script. The only oddity was that I got an error on the confirmation page. I ignored it because I was restoring another site and was in a hurry to get the site up again. If I encounter this again I will check the log and share anything I see there. enable_discourse_id: Failed to automatically register with Discourse ID. This could be due to network connectivity issues, firewall restrictions, or the Discourse ID service being unreachable. Please check server logs for more details or contact support." [Screenshot 2026-01-27 at 8.55.34 AM]

Is your site behind a firewall or have some dns issue?

not that I am aware of! when I replaced app.yml and then rebuilt, then restored my backup, everything was fine. but I don’t use discourse ID on my personal site. :person_shrugging:

Did you give the install script your SMTP credentials? Maybe you didn’t since you were going to copy your app.yml anyway, and if you don’t then it defaults to using discourse_id.

No, I did not. I had declined to set up SMTP during the installation.

I think your best bet is to check /logs, there should be an error entry there related to Discourse ID. (I moved this to a separate topic since it isn’t related to the announcement.)

I looked in logs but too late.. after restoring my backup. I don’t see anything about this issue in the logs now. It’s no longer a problem for me personally. Hetzner also has a limit of 5 servers for new customers, and I have reached that limit! So I can’t just try again with a new server currently. As soon as I can I will do so.

AH, ok. In that case, you can try this: Changing domain names prevents Discourse ID from working - #3 by 在云端_裸奔 and once done, toggle Discourse off/on in the admin UI. It should either just work or trigger the same error again in /logs.

Actually, just checking and see that Discourse ID already works on my site now. As I said, I restored my site so this is no longer a problem for this site. But I am curious to see what would happen if I repeated the steps to create a new site which I will do as soon as hetzner lets me! Maybe after I pay them for my first invoice next week on 1 February. Could this have been related to the fact that I changed the IP for the domain at namecheap not long before spinning up the site? Maybe the domain wasn’t resolving to the new IP for everybody yet.

[imagen] tobiaseigen: I had declined to set up SMTP during the installation. Then it is expected that it would try to install discourse_id. Did you have the DNS for the domain pointing to the new site when you ran discourse-setup-ruby? [imagen] tobiaseigen: Could this have been related to the fact that I changed the IP for the domain at namecheap not long before spinning up the site? Maybe the domain wasn’t resolving to the new IP for everybody yet. That’s my guess.

[imagen] pfaffman: Did you have the DNS for the domain pointing to the new site when you ran discourse-setup-ruby? Yep! I ssh’ed into the domain name so it was definitely working for me. But I suspect it was not yet working for Discourse ID.

Problemas de configuración de ID de Discourse en Hetzner

Soporte del producto

pfaffman (Jay Pfaffman) 27 Enero, 2026 16:50 3

¿Su sitio está detrás de un cortafuegos o tiene algún problema de DNS?

Tema		Respuestas	Vistas
Failed to automatically register with Discourse ID Self-hosting	10	383	27 Mayo 2026
Help with setting up Discourse ID Product Support unsupported-install , discourse-id	28	1087	19 Noviembre 2025
Ports blocked (Hetzner cloud server) Self-hosting	16	10156	26 Abril 2022
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	1092	22 Octubre 2025
Can't set up Discourse ID: Application with this redirect URI already exists Self-hosting discourse-id	3	158	19 Marzo 2026

Problemas de configuración de ID de Discourse en Hetzner

Temas relacionados