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

Welcome E-mail confirm link opens forum on port 4567

Technical Support

562

T
tmikey last edited by

I'm using NGINX as a reverse proxy for nodebb but for some reason the links inside the e-mails try to open the forum on port 4567 instead. How do I fix this? Thanks.
1 Reply Last reply
Reply Quote 0
Julian Lam GNU/Linux Admin last edited by

You'll want to make sure url in your config.json is set properly without the port number.
1 Reply Last reply
Reply Quote 1
T
tmikey last edited by

Thanks Julian! That fixed it.
1 Reply Last reply
Reply Quote 0

Suggested Topics

Nodebb only starts in dev mode on live forum
Technical Support • • William Robin

1

0
Votes

1
Posts

329
Views

Hey there!

I have a nodebb instance i've been customizing through theming and plugins.

I recently came across an issue that has prevented me from running ./nodebb start

Clustering enabled: Spinning up 4 process(es).
2019-07-22T06:23:35.139Z [4567/15633] - [32minfo[39m: Initializing NodeBB v1.12.2 https://kratomwatchdog.com 2019-07-22T06:23:35.431Z [4567/15633] - [31merror[39m: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.443Z [4567/15633] - [31merror[39m: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.446Z [4568/15638] - [31merror[39m: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.448Z [4568/15638] - [31merror[39m: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.449Z [4569/15640] - [31merror[39m: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} [cluster] Child Process (15633) has exited (code: 0, signal: null) 2019-07-22T06:23:35.454Z [4569/15640] - [31merror[39m: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15638) has exited (code: 0, signal: null) [cluster] Child Process (15640) has exited (code: 0, signal: null) 2019-07-22T06:23:35.462Z [4570/15645] - [31merror[39m: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.464Z [4570/15645] - [31merror[39m: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15645) has exited (code: 0, signal: null)
I am able to run nodebb in dev mode, and have had to run it in a screens session to keep the forum online until i'm able to resolve the issue.
N

All links under Admin->Manage don't work
Technical Support • • nmeadows

12

0
Votes

12
Posts

149
Views

@nmeadows said in All links under Admin->Manage don't work:

@gotwf I have found the culprit, and it has nothing to do with NodeBB, so I'm sorry to have bothered you.
It ended up being our security team turned on web filtering rule on our load balancer that filters out certain URL paths that have admin/manage/etc in the path. The idea being to filter our administration pages and force the use of VPN to get to those paths. It's a fine idea, but I was not informed of that change.

Thank you for your help.

Better to bother us and get it fixed than to not bring it up and not 🙂 Glad that you got it figured out.
F

Port :4567 in link in website sitemap
Technical Support • • ForoTele

4

0
Votes

4
Posts

107
Views

@ForoTele fix the url value in config.json, it should be set to exactly the same url at which you access your site
?

Solved BUG. Incorrect display of links in chat
Technical Support • bug • • A Former User

2

0
Votes

2
Posts

1234
Views

?

upload-3e2e4d8c-f9f5-4d63-84b9-adda0250ff8d
Creating a Sub Domain and linking my forum to it
Technical Support • • Dan Pereira

4

0
Votes

4
Posts

900
Views

@julian

Hahaha, good question. I didn't even notice. I just googled for the documentation to get to it quickly. I didn't even pay attention to the URL.

Welcome E-mail confirm link opens forum on port 4567

Suggested Topics

Nodebb only starts in dev mode on live forum
Technical Support • • William Robin

All links under Admin->Manage don't work
Technical Support • • nmeadows

Port :4567 in link in website sitemap
Technical Support • • ForoTele

Solved BUG. Incorrect display of links in chat
Technical Support • bug • • A Former User

Creating a Sub Domain and linking my forum to it
Technical Support • • Dan Pereira

Get Started

Resources

Company

Welcome E-mail confirm link opens forum on port 4567

Suggested Topics

Nodebb only starts in dev mode on live forum Technical Support • • William Robin

All links under Admin->Manage don't work Technical Support • • nmeadows

Port :4567 in link in website sitemap Technical Support • • ForoTele

Solved BUG. Incorrect display of links in chat Technical Support • bug • • A Former User

Creating a Sub Domain and linking my forum to it Technical Support • • Dan Pereira

Get Started

Resources

Company

Nodebb only starts in dev mode on live forum
Technical Support • • William Robin

All links under Admin->Manage don't work
Technical Support • • nmeadows

Port :4567 in link in website sitemap
Technical Support • • ForoTele

Solved BUG. Incorrect display of links in chat
Technical Support • bug • • A Former User

Creating a Sub Domain and linking my forum to it
Technical Support • • Dan Pereira