Dominio onion de TOR para Discourse

Soporte
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

Sé que este hilo es antiguo, pero tenía el mismo problema y tuve que hacer algunos ajustes para que funcionara.

Lo que sucede es que verifiqué con ./launcher logs app y resulta que la plantilla onion copia un montón de cosas del sitio predeterminado; el problema es que algunas de estas configuraciones están duplicadas.

Tuve que iniciar sesión en el contenedor con ./launcher enter app y luego editar /etc/nginx/conf.d/onion.conf para eliminar la línea proxy_buffer_size 8k;.

Adicionalmente, tuve que agregar server_names_hash_bucket_size 64; al archivo nginx.conf.

Esto hizo que el servidor volviera a funcionar; lo descubrí revisando los registros.

6

Dado que el proyecto Tor ahora tiene documentación sobre la cabecera Onion-Location, me gustaría saber cómo es posible configurar Discourse para que sirva tanto un “dominio superficial” como una dirección .onion.

Parece que los ajustes de @BryanHR se pueden realizar en la configuración YAML del contenedor. Supongo que la cabecera Onion-Location se podría añadir de la misma manera.

Sin embargo, recuerdo que Discourse está vinculado a su host original, por lo que me preocupa que el acceso a un sitio .onion sirva recursos a través de HTTP o HTTPS normal sin pasar por la red Tor. (Por ejemplo, la solicitud original se realiza a través de Tor, pero el JavaScript utiliza el dominio original para obtener recursos adicionales).