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. I…

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…

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 …

[image] 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.

Discourse ID setup issues on Hetzner

Product Support

pfaffman (Jay Pfaffman) January 27, 2026, 5:36pm 11

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?

That’s my guess.

Topic		Replies	Views
Failed to automatically register with Discourse ID Self-hosting	10	341	May 27, 2026
Help with setting up Discourse ID Product Support unsupported-install , discourse-id	28	1030	November 19, 2025
Ports blocked (Hetzner cloud server) Self-hosting	16	10113	April 26, 2022
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	1036	October 22, 2025
Can't set up Discourse ID: Application with this redirect URI already exists Self-hosting discourse-id	3	149	March 19, 2026

Discourse ID setup issues on Hetzner

Related topics