The truth is that we’re a non-profit with a relatively small team and limited resources, self-hosting the forum isn’t a trivial task, and Discourse very generously offered to host it for free. However this was always the plan if the forum’s launch was received positively by the community, and we’re pleased to have seen it go so well <3
We’ve completed the migration.
The forum is also (experimentally) now available at https://v236xhqtyullodhf26szyjepvkbv6iitrhjgrqj4avaoukebkk6n6syd.onion/
Let us know if you encounter any issues!
1 reply
It’s normal for the DNS changes to take a bit of time to propagate across the Internet. As a rule of thumb, it can take up to 72 hours. So, if after a few days, forum.torproject.net still points to the Discourse-hosted forum, it may indicate a misconfigured DNS server, or some other problem.
@lavamind look like DNS is fine, but certificates are not fine:
d:\curl>curl -v https://forum.torproject.net
* Trying [2620:7:6002:0:466:39ff:feb6:d569]:443...
* Connected to forum.torproject.net (2620:7:6002:0:466:39ff:feb6:d569) port 443
(#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* CAfile: d:\curl\curl-ca-bundle.crt
* CApath: none
* [CONN-0-0][CF-SSL] TLSv1.0 (OUT), TLS header, Certificate Status (22):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Client hello (1):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Certificate Status (22):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Server hello (2):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Certificate (11):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, CERT verify (15):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN=forum.torproject.org
* start date: Jun 15 20:41:40 2023 GMT
* expire date: Sep 13 20:41:39 2023 GMT
* subjectAltName does not match forum.torproject.net
* SSL: no alternative certificate subject name matches target host name 'forum.t
orproject.net'
* Closing connection 0
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name
'forum.torproject.net'
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Ah ha, that was caused by our redirection vhost not listening on the
IPv6 socket. I’ve fixed it so the redirection should work now. Thanks
for looking into it! 
Congratulations on the successful migration! I have been able to switch my 2FA by using a backup recovery code and things seem to be working fine.
Good job!
using the .onion-address of the forum for quoting does not work properly (copy & paste the link of the thread as .onion)
(probably because the forum software can’t resolve the links - and presumably users who do not use .onion can’t access it either)
[sorry for being lazy to report on GitLab]