@dunlix (and others)
Thanks, the disable plugins suggestion worked. Apparently it was the "sanitize html" plugging that was causing the problem.
Not even sure why we had that still installed.
Thanks all for the troubleshooting help!
I just set up my forum, but when users try registering, and enter all of their infos, they get the red Registration error message, with HTML code of CloudFlare's 502 page and then temporairly get disconnected from the server, reconnecting back instantly. I am using NGINX as a reverse proxy, with CloudFlare's CDN and TLS, and TLS is forced. You can try replicating the error yourself on https://darkfires.org/register
An errors client-side? My hunch is that cloudflare is interrupting socket connections
This is just crazy... i disabled CloudFlare. But when i try registering now, i get <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head> <title>500 — Internal Server Error</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <meta name="description" content="500 - Internal Server Error"/> <style type="text/css"> body {font-size:14px; color:#777777; font-family:arial; text-align:center;} h1 {font-size:180px; color:#99A7AF; margin: 70px 0 0 0;} h2 {color: #DE6C5D; font-family: arial; font-size: 20px; font-weight: bold; letter-spacing: -1px; margin: -3px 0 39px;} p {width:375px; text-align:center; margin-left:auto;margin-right:auto; margin-top: 30px } div {width:375px; text-align:center; margin-left:auto;margin-right:auto;} a:link {color: #34536A;} a:visited {color: #34536A;} a:active {color: #34536A;} a:hover {color: #34536A;} </style> </head> <body> <p><a href="http://darkfires.org/">darkfires.org</a></p> <h1>500</h1> <h2>Internal Server Error</h2> <div> Something went wrong. Please try your request again. </div> </body> </html>
. It cant be a CF issue, and i get quickly disconnected and reconnected when pressing Register.
@hungrybeast can you try looking in the NodeBB error log?
Nevermind, the spam-be-gone plugin was causing it. Heres what i found in the console.
at new ClientRequest (_http_client.js:52:11)
at Object.exports.request (http.js:31:10)
at Object.exports.request (https.js:199:15)
at module.exports (/opt/nodebb/node_modules/simple-recaptcha-new/index.js:37:23)
at Object.Plugin._recaptchaCheck (/opt/nodebb/node_modules/nodebb-plugin-spam-be-gone/library.js:282:3)
at /opt/nodebb/node_modules/nodebb-plugin-spam-be-gone/library.js:211:11
at /opt/nodebb/node_modules/async/lib/async.js:718:13
at async.forEachOf.async.eachOf (/opt/nodebb/node_modules/async/lib/async.js:233:13)
at _parallel (/opt/nodebb/node_modules/async/lib/async.js:717:9)
at Object.async.parallel (/opt/nodebb/node_modules/async/lib/async.js:731:9)
at Object.Plugin.checkRegister [as method] (/opt/nodebb/node_modules/nodebb-plugin-spam-be-gone/library.js:206:8)
at /opt/nodebb/src/plugins/hooks.js:120:12
at /opt/nodebb/node_modules/async/lib/async.js:375:13
at iterate (/opt/nodebb/node_modules/async/lib/async.js:262:13)
at Object.async.forEachOfSeries.async.eachOfSeries (/opt/nodebb/node_modules/async/lib/async.js:281:9)
at Object.async.inject.async.foldl.async.reduce (/opt/nodebb/node_modules/async/lib/async.js:374:15)
at fireFilterHook (/opt/nodebb/src/plugins/hooks.js:112:9)
at Object.Plugins.fireHook (/opt/nodebb/src/plugins/hooks.js:93:4)
at /opt/nodebb/src/controllers/authentication.js:76:12
at fn (/opt/nodebb/node_modules/async/lib/async.js:746:34)
at /opt/nodebb/node_modules/async/lib/async.js:1213:16
at /opt/nodebb/node_modules/async/lib/async.js:166:37
Seems like the recaptcha wasnt coded correctly. Or i didnt set it up correctly