Actually I managed to get it to work on the phone by upgrading Chrome. According to caniuse, optional chaining became available in Chrome 80. In theory compatibility should extend all the way down to Kitkat. The lack of transpiling is a bit concerning though.
Nodebb in tor works!
-
Re: Running nodebb in tor
As far as i can see everything works fine. -
I'm create a NodeBB community mirror
in onion for the test, not bad, but in console have more errors when open /recent or /category pages with topics list.
https://rrjybnxgjelnxsnq4jsctsznhhgugq4kmqy44qtl7eeqnn6u5o5yrwad.onion
TypeError: obj is undefined getSafeMethod moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:230 patch moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/media.js:90 mozPatch moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/media.js:97 modifyWindow moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:263 patchAll moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:296 Patching frames[0] patchWindow.js:298:19
TypeError: win[(("HTML" + (intermediate value)) + "Element")] is undefined modifyFramingElements moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:288 modifyWindow moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:265 patchAll moz-extension://4ba86e3a-159e-2d43-8dac-c9b075149702/nscl/content/patchWindow.js:296 Patching frames[0]
and alert about html5 canvas image data
Setting in Tor
SL: Safer
NoScript: blocked 0 -
-
@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?
-
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? -
Version 3.1.4 works!