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

NodeBB: Search Bar Widget Error

Technical Support

F
fayez last edited by

I am getting this error while searching...
GET http://localhost:4567/api/search/?term=we&in=titlesposts 404 (Not Found)
1 Reply Last reply
Reply Quote 0
PitaJ Global Moderator Plugin & Theme Dev last edited by

Works fine here: https://community.nodebb.org/api/search/?term=we&in=titlesposts

Perhaps you don't have the search plugin enabled?
1 Reply Last reply
Reply Quote 0
F
fayez last edited by

I have enabled the plugin. Is there any issues related to plugin version or the search is database(mongo/redis) dependent? Need help.
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

272
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.
G

[nodebb-plugin-emoji-extended] Bad URL
Technical Support • • Guiri

2

0
Votes

2
Posts

926
Views

A

Change your config.json to domain.com:4567

Then use nginx to forward reverse proxy 80 to port 4567 using the example in NodeBBs documentation
C

Ubuntu 16.04 executing '/path/to/nodebb start' causes error
Technical Support • • Crayz

4

0
Votes

4
Posts

1011
Views

C

@PitaJ Worked, thanks 🙂 For some reason I had the idea cd wouldn't work there
Running NodeBB on IIS
Technical Support • windows nodebb publishing iis • • SergioNG

5

0
Votes

5
Posts

3648
Views

C

Hi all,

I realize this is an old topic, but given that I'm dealing with exactly the same problem, I figured it would be sensible to reply here. Essentially, I've followed the advice of @pichalite and created a simple IIS forward proxy for my NodeBB server. Unfortunately this solution does not yield the desired result, as many requests for resources are not being made to the correct directory - instead, requests are being made to the root level of the IIS Web server (e.g., GET http//website.ca/stylesheet.css?4210ebb0-9225-4237-b2ad-87d88b61756b), and not to the specified port where NodeBB is being hosted (e.g., http://website.ca:4567 or http://localhost:4567).

Any ideas? I've played around with reverse proxies and outbound rules to route all outgoing traffic from http://localhost:4567 to the same URL I've specified for the proxy rule (e.g., http//website.ca/associates-hub) to no avail... If more info or screenshots are needed, they can be provided. I've been banging my head against the wall trying to cycle through all possible solutions to this problem. Any insight would be GREATLY appreciated.

Thanks,

Cam
Can I use my users' data to log in Nodebb directly?
Technical Support • • shukun zhang

2

0
Votes

2
Posts

65
Views

Not sure what you mean. What data? Don't they log into NodeBB directly already?

| |

1 / 1

NodeBB: Search Bar Widget Error

Suggested Topics

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

[nodebb-plugin-emoji-extended] Bad URL Technical Support • • Guiri

Ubuntu 16.04 executing '/path/to/nodebb start' causes error Technical Support • • Crayz

Running NodeBB on IIS Technical Support • windows nodebb publishing iis • • SergioNG

Can I use my users' data to log in Nodebb directly? Technical Support • • shukun zhang

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

[nodebb-plugin-emoji-extended] Bad URL
Technical Support • • Guiri

Ubuntu 16.04 executing '/path/to/nodebb start' causes error
Technical Support • • Crayz

Running NodeBB on IIS
Technical Support • windows nodebb publishing iis • • SergioNG

Can I use my users' data to log in Nodebb directly?
Technical Support • • shukun zhang