TOR-Onion-Domain für Discourse

Unterstützung
1

Hello,

we are having some issues for users to connect to our discourse instance through TOR. Many times, a “Unable to connect” message appears and you have to change several times your identity to connect. We have checked with our upstream hosting provider and they say they dont block tor traffic so we are trying to figure out what it could be. We have generated an onion domain for the platform but, at the same time, we want users to be able to access through a reserved domain with a non-tor browser.

Any suggestions?

Thanks in advance

2

This means your instance is launched as an onion site, and as such, cannot be viewed or accessed with a non-tor browser.

Onion sites can only be accessed through tor-browsers, but if you want your discourse instance to be accessed outside its onion domain, then you will need to get a premium domain for the ‘surface web’ like a .com,.org, .ly, etc. When you do this, then you can map the domain you bought with your discourse instance through its IP address.

I hope this is clear enough, huh?

3

Hello,

yes, we have a premium domain configured already. What we want to achieve is that you can access to the platform both through the premium domain (this is what is working) and an onion domain (we have created the onion domain; configured tor on the servers; configured nginx) at the same time. We included in the server_name paramater the onion domain but this doesnt seem to be enough.

Thanks.

4

Oh,never knew this was what you requested. I had thought in the reverse.

For your present condition, please see this.I hope it explains what you need to do better.

5

Ich weiß, dass dieser Thread uralt ist, aber ich hatte das gleiche Problem und musste einige Anpassungen vornehmen, damit es funktioniert.

Das Problem ist, dass ich mit ./launcher logs app geprüft habe und sich herausstellte, dass die Onion-Vorlage eine Menge Dinge von der Standardseite kopiert. Das Problem dabei ist, dass einige dieser Einstellungen dupliziert sind.

Ich musste mich mit ./launcher enter app im Container anmelden und dann die Datei /etc/nginx/conf.d/onion.conf bearbeiten, um die Zeile proxy_buffer_size 8k; zu löschen.

Außerdem musste ich server_names_hash_bucket_size 64; zur Datei nginx.conf hinzufügen.

Dadurch funktioniert der Server wieder. Ich habe das herausgefunden, indem ich mir die Logs angesehen habe.

6

Da das Tor-Projekt nun eine Dokumentation zum Header Onion-Location bereitstellt, würde mich interessieren, wie man Discourse so konfigurieren kann, dass es sowohl eine „Surface-Domain