@eeeee I totally agree less frameworks , then all stable and better.

Let me confirm that the latest version of 3.1.4 works in tor too.

So finally i figure it out and i run latest version of nodebb, there were problems with my build!
Due to one outdated optional plugin shxxt, yes it did got messy , i back up my uploads directory and deleted whole nodebb directory and then done git clone from the latest upstream of v3.x branch, then copied old upload directory and json.config back, still i feel uneasy about whole socket.io stuff.
Besides of that i think that it will be good idea to make better control of plugins like some script which checks after new plugin build if nodebb.min.js generated , because in my case one of plugins did actually broken the build of nodebb.min.js , it wasn't generated at all and i didn't seen any warnings about it.
Yes the nodebb version 3.1.4 works in Tor too, but let me point that Nginx configuration still a potential source of errors and i spent some quality time setting this up, again and again

@brazzerstop Do you run your forum in Tor? How do you generate those csrf tokens?
Soon, there will be out version 3.1.5 and then 3.2 , it would be interesting to know if my issues with socket.io addressed, i look into git and saw some commits , we just need to wait and test.

when i run try.nodebb.org via my tor browser , everything seems ok

@brazzerstop It works, because i run version 3.1.2 and thanks for putting it out here , my original questions was , what about future versions , how i can generate the csrf token, because in 3.1.3 and upwards it would work only if csrf provided?

You mean this https://rrjybnxgjelnxsnq4jsctsznhhgugq4kmqy44qtl7eeqnn6u5o5yrwad.onion , this even not opening.
Ok i opened this forum in Tor browser https://community.nodebb.org and observe following:
https://community.nodebb.org/socket.io
?_csrf=7000da5c5eb90fcc61cbb668b84bc7d762c3d7bb76d1a9394168613a037a09d68ab1021e40d3edfa677f0ff96db394124f823085daf5e7806f76f50974aa1d .
In my case my forum does not generate csrf, so what should i do?
I looked the config.json, but there not description how to enable it.
Is this some special Nginx issue? Because i use it behind my forum in Tor and it works only with version 3.1.2.
I dont consider that devs decision to use socket.io make sense to me, personally i dont see a use case for such feature.

Hi all!
I just want to say my two cents about socket.io and Tor , it's seems to me really a puzzle, because currently only version 3.1.2 works with Tor, but it took some time and adjustment to make it run.
Especially on Nginx side, i will not mention what i gone trough, but i think if the devs of nodebb clearly can point why they don't consider Tor as theirs major group of users than i would understand and appreciate the feedback.
Is this how the current development of nodebb would continue in the future?
If Tor not supported fully, well i must think about fork for the Tor case usage Nodebb, it's clearly not what i wish or have time for, but if the situation with Tor support not improve i will consider to do the fork of the NodeBB for Tor.

I am running now 3.1.4 works in Tor.

Version 3.1.4 works!

Ok on 3.1.2 everything works!

@PitaJ Yes, this did not worked for me.
I run Nginx as reverse proxy with the setup from the nodebb docu, i have SSL certificate which works in tor.
What i need that,that somebody show me the example configs so that i would test it in my environment.
Both for Nginx and the nodebb and the tor.
Or somebody should tell me why all those /socket.io/?EIO=4 403 Forbidden responses are generated and why csrf missing?

it got even worse, i can login, but any changes in admin preferences are not saved, devs please fix this bug or provide workaround.

For some strange reasons, your brazzerstop onion generates csrf tokens and my not , what i am doing wrong?
Ok, now i have nginx installed with the same issuer and my SSL certificate works in my nginx , but this is already overkill.

I have no clue what do next, maybe my torrc must be adjusted for socket.io i dont know.
I assume my tor configuration wont put trough the sock requests.
I need help, somebody should me explain how to enable csrf an why socket.io unable to connect?

@brazzerstop said in Nodebb in tor works!:

https://rrjybnxgjelnxsnq4jsctsznhhgugq4kmqy44qtl7eeqnn6u5o5yrwad.onion

Cool, at least now somebody can reproduce bugs which i get with latest's version.
How do you configure the socket.io?

Show me your config.json ,

this what i have in my ( some data omitted for anonimity concerns)

"url": "http://pathtomyonion.onion",
    "secret": "secret",

I dont run nginx , should it try to do it?

look what now my server saying
info: [socket.io] Restricting access to origin: i have ommited full address .onion:*
And i still receive same failure message

403 means that my server recognise the request, but for some unknow to me reason it refuse to forward further.

I use latest tor browser and upgraded nodebb engine to 3.1.3 recently released version.
I am experience problems with CORS, can somebody help?

I am getting error socket.io/?EIO=4&transport=polling&t= 403 Forbidden
My node server somehow refuses to authorize it socket.io request .

Add to this list organization Independent republic of Siberia !

Ok, fine, but still it's strange i prefer convention over verbosity.

Sure my problems appeared only after i installed 3.x, because early the plugins devs did not provided newer versions of theirs plugins for the newer nodebb version, i admit it's my fault , because i didn't knew about big changes in v3.x

Now i took the package.json from the github branch 3.x install directory and deleted all npm modules and the file package-lock.json in my current nodebb, so after all work i found that my default composer was disabled , now it is enabled and here the outcome :

It looks like, now it works finally!
Strange that my default composer was disabled, but now it is enabled.
I will report if i find any breaking issues with the plugins, i hope that i wont find any breaking issues.

So far i like what i see, it really fast , the performance in Tor is fast as lightning thanks! Great job overall!!!

Here another blocker issue which i have with latest nodebb 3.X version

Whenever i click on the menus , i dont see page change and drop down menu is not loaded