Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

unable to get nginx working with nodebb

Technical Support

2

2

160

Log in to reply

N

Nam Vu GNU/Linux @Todd
last edited by

@Todd mine sharing with us your new config?
J 1 Reply Last reply
Reply Quote 0
J

julian GNU/Linux Admin @Nam Vu
last edited by

Hi @Nam-Vu, some example working configurations can be found here https://docs.nodebb.org/configuring/proxies/nginx/

If your config is not working, please paste it here for us to review. Thanks!
1 Reply Last reply
Reply Quote 0

Suggested Topics

M

Unsolved Installing NodeBB on Google Compute Engine or Cloud Run

Technical Support
• • manoj

5

0
Votes

5
Posts

252
Views

M

@manoj

How To Install NodeBB on Google Compute Engine | GCP | Google CloudSQL | Nginx
R

Running NodeBB on multi core CPU

Technical Support
• • Raj

8

0
Votes

8
Posts

417
Views

S

@Raj said in Running NodeBB on multi core CPU:

@PitaJ Thanks. As I have 8 core CPU I want my NodeBB to use all of them. But by default NodeBB is using only one core!

Are you running your reverse proxy, SSL handling, or database on the same box? If so, you definitely don't want all of them for NodeBB.

Even if you aren't, why do you have so many cores, and what are you doing that makes you want to scale like this? How busy is your site? We've topped 191 million hits in a single month on a single core and aren't even working hard.
E

Setting up a local environment of nodebb causes some weird errors from dbsearch

Technical Support
• • ende124

8

0
Votes

8
Posts

430
Views

P

I don't think that commit has been released yet, which would explain why you'd still have the error. You could have just cherry-picked that commit you linked, but what you did works as well. It might just end up conflicting with future upgrades.
S

nodebb install - Failed to serialize user into session

Technical Support
• • startech

6

0
Votes

6
Posts

2693
Views

S

NodeBB version: NodeBB-NodeBB-v0.6.1-0-g4686ae9
K

400 and 522 errors since enabling SSL via Nginx proxy

Technical Support
• • KingCat

14

1
Votes

14
Posts

9873
Views

K

Welp, I solved it.

Turns out I had the wrong directory specified in nginx for static assets. It was pointing to a different install of nodebb. For some reason that caused issues with socket.io (and only with safari/opera for some reason).

Now, here's the weird thing. I only recently started using nginx to serve the assets. Recently as in like this morning. Before that I simply had a proxy pass setup and let nodebb serve the assets. I'm not sure what was causing the 400/502 errors then but I'm just glad their solved now.

| | | |

Copyright © 2022 NodeBB | Contributors

1 / 1