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).

How to configure nginx to proxy to 4567

Technical Support

719

A
abhinov singh @julian last edited by

@julian How to configure your server so that it will redirect your subdomain to the correct port (:4567). I also made changes to config.json , but what next .
1 Reply Last reply
Reply Quote 0
Julian Lam GNU/Linux Admin last edited by

Please consult the nginx documentation: https://docs.nodebb.org/configuring/proxies/nginx/
1 Reply Last reply
Reply Quote 0

Suggested Topics

Guide correction: Apache2.4 Proxy config is innaccurate
Technical Support • • W0org42 W0org42

3

1
Votes

3
Posts

1191
Views

I have submitted the change.
[Solved] URL Forwarding error after install with VestaCP (Nginx Proxy)
Technical Support • • Valentine Solo

10

0
Votes

10
Posts

3103
Views

@pitaj vestacp has several nginx.conf. As I mentioned I edited "site-specific" config in /home/admin/conf/web where vestacp keeps configs for all hosts, inculding ssl and lets encrypt.
Maybe you mean global nginx.conf which is located in /etc/nginx ? I did no changes in it.
T

Welcome E-mail confirm link opens forum on port 4567
Technical Support • • tmikey

3

0
Votes

3
Posts

562
Views

T

Thanks Julian! That fixed it.
NodeBB, Docker-Compose, MongoDB, Nginx - Only showing Login/Register and NodeBB name
Technical Support • • MostHated

4

0
Votes

4
Posts

370
Views

Edit : I gave it a few minutes after restarting Nginx and it looks like using the files from Github was my fix, looks to be that everything is working now!

After doing a git clone of the current repo and building with the Dockerfile as opposed to just using the currently available nodebb/docker on docker hub, it looks like those issues went away. It currently isn't displaying anything at all right now, but in the logs I see:
nodebb | nodebb | Starting NodeBB nodebb | "./nodebb stop" to stop the NodeBB server nodebb | "./nodebb log" to view server output nodebb | "./nodebb help" for more commands nodebb | nodebb | NodeBB v1.12.0 Copyright (C) 2013-2014 NodeBB Inc. nodebb | This program comes with ABSOLUTELY NO WARRANTY. nodebb | This is free software, and you are welcome to redistribute it under certain conditions. nodebb | For the full license, please visit: http://www.gnu.org/copyleft/gpl.html nodebb | nodebb | Clustering enabled: Spinning up 1 process(es). nodebb | 2019-04-04T22:33:50.921Z [4567/22] - info: Initializing NodeBB v1.12.0 https://forum.mysite.dev nodebb | 2019-04-04T22:33:54.634Z [4567/22] - info: [socket.io] Restricting access to origin: https://forum.mysite.dev:* nodebb | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules/helmet/index.js:33:28 nodebb | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "setIf" parameter is deprecated. Refer to the documentation to see how to set the header conditionally. at node_modules/helmet/index.js:33:28 nodebb | 2019-04-04T22:33:54.961Z [4567/22] - info: Routes added nodebb | 2019-04-04T22:33:54.969Z [4567/22] - info: NodeBB Ready nodebb | 2019-04-04T22:33:54.976Z [4567/22] - info: Enabling 'trust proxy' nodebb | 2019-04-04T22:33:54.986Z [4567/22] - info: NodeBB is now listening on: 0.0.0.0:4567
Domain configuration-> Digitalocean + Ubuntu with NodeBB installed
Technical Support • • remcokatz

7

0
Votes

7
Posts

2699
Views

Ok so after having a chat with nhl.pl it seems that the ip for the proxy_pass in the nginx file should be "localhost" instead of "127.0.0.1" because of reasons (digitalocean).

config.json:

{
"url": "http://ideocracycommunity.com:4567",
"secret": "lolololol",
"database": "redis",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "lololoo",
"database": "0"
}
}

nginx:

server {
listen 80;
server_name ideocracycommunity.com;
location / { proxy_pass http://localhost:4567; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade;
}
}

How to configure nginx to proxy to 4567

Suggested Topics

Guide correction: Apache2.4 Proxy config is innaccurate
Technical Support • • W0org42 W0org42

[Solved] URL Forwarding error after install with VestaCP (Nginx Proxy)
Technical Support • • Valentine Solo

Welcome E-mail confirm link opens forum on port 4567
Technical Support • • tmikey

NodeBB, Docker-Compose, MongoDB, Nginx - Only showing Login/Register and NodeBB name
Technical Support • • MostHated

Domain configuration-> Digitalocean + Ubuntu with NodeBB installed
Technical Support • • remcokatz

Get Started

Resources

Company

How to configure nginx to proxy to 4567

Suggested Topics

Guide correction: Apache2.4 Proxy config is innaccurate Technical Support • • W0org42 W0org42

[Solved] URL Forwarding error after install with VestaCP (Nginx Proxy) Technical Support • • Valentine Solo

Welcome E-mail confirm link opens forum on port 4567 Technical Support • • tmikey

NodeBB, Docker-Compose, MongoDB, Nginx - Only showing Login/Register and NodeBB name Technical Support • • MostHated

Domain configuration-> Digitalocean + Ubuntu with NodeBB installed Technical Support • • remcokatz

Get Started

Resources

Company

Guide correction: Apache2.4 Proxy config is innaccurate
Technical Support • • W0org42 W0org42

[Solved] URL Forwarding error after install with VestaCP (Nginx Proxy)
Technical Support • • Valentine Solo

Welcome E-mail confirm link opens forum on port 4567
Technical Support • • tmikey

NodeBB, Docker-Compose, MongoDB, Nginx - Only showing Login/Register and NodeBB name
Technical Support • • MostHated

Domain configuration-> Digitalocean + Ubuntu with NodeBB installed
Technical Support • • remcokatz