Is Sam's multi-hostname ninja plugin approach still valid?

Continuing the discussion from Forcing hostname has broken support for Onion Services:

We have a use case where, like an onion+clearnet usage, we need two different hostnames for the same Discourse instance. Before we spend some time testing, just wondered if anyone has a feeling whether or not the approach below would still be valid. (Since it’s been a couple years.)

2 Likes

I think DISCOURSE_BACKUP_HOSTNAME environment variable may work for this now due t

3 Likes

Hey that’s worth a try and obviously much simpler. We’ll take a look and report back.

For our purposes it seems to have gotten the job done. Thanks!

Hi @downey @Falco,

Can you share with us the guide in using DISCOURSE_BACKUP_HOSTNAME
with tor setup ?

I’m currently make it last year; but now i have some conflicts with connecting onion container with the nginx configuration… i’m getting empty page for onion address

ERR_EMPTY_RESPONSE

Thank you.

Hi.
Is it still valid?

Hi. everybody.
I want to use the onion address in my discourse forum.
I referenced several articles and installed tor, it works well.
Thank you to Bryan, pfaffman, Falco .

Now when I input an onion address in the Tor browser, it redirects to the clearnet address and then there is no need to use tor.
I know using 2 domains is not a preferable way. However I need to use onion addresses on my forum and want to implement this function. sam introduced a method using plugins, and Falco introduced the DISCOURSE_BACKUP_HOSTNAME env variable method.
I tried using sam’s plugin method, it is not working.
I never tested DISCOURSE_BACKUP_HOSTNAME method.
Please advise in this problem.
Thank you.