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

Are there any doc of the nodebb's API?

General Discussion

1377

Jam last edited by

Hi, Are there any doc of the nodebb's API?

Not the https://docs.nodebb.org and https://github.com/NodeBB/NodeBB/wiki/Hooks, just like describing the topics.getTopicsByTids, db.getSortedSetRangeByScore and so on~

Thanks~
1 Reply Last reply
Reply Quote 2
Timothy Fike Community Rep last edited by

Not yet.
1 Reply Last reply
Reply Quote 0
Jam last edited by
1 Reply Last reply
Reply Quote 3
Julian Lam GNU/Linux Admin @Jam last edited by

@Jam It's being discussed here: https://github.com/NodeBB/NodeBB/issues/4750

jsumners created this issue in NodeBB/NodeBB

closed API documentation #4750
1 Reply Last reply
Reply Quote 3
Jam @julian last edited by

@julian thanks, i got it~
1 Reply Last reply
Reply Quote 0

Suggested Topics

Nodebb 插件列表太难用
General Discussion • • Ivorzk

4

1
Votes

4
Posts

91
Views

@julian 谢谢！ thank you
A

Can access NodeBB installation from localhost only
General Discussion • • afe123

2

0
Votes

2
Posts

924
Views

A

Hmm. I figured it out. My miniscule understanding of iptables does not allow me to explain this, but if I move the rule for port 4567 up in the chain, it works. I thought they should just be going down the chain rules. Missing something here. Anyway, the issue seems to be resolved. If someone could explain why - this would be interesting to know.

Chain INPUT (policy pkts bytes target prot opt in 2590K 1747M ACCEPT all -- * 159 13356 ACCEPT icmp -- * 222 13300 ACCEPT all -- lo 25 1420 ACCEPT tcp -- * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 54 2736 ACCEPT tcp -- * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * 574 45099 ACCEPT udp -- * 0 0 ACCEPT udp -- * * 11540 1407K REJECT all -- * 0 0 ACCEPT tcp -- * * 0 0 ACCEPT tcp -- * * ACCEPT 0 packets, 0 bytes)
out source destination
* 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
* 0.0.0.0/0 0.0.0.0/0
* 0.0.0.0/0 0.0.0.0/0
* 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:4567
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2080
* 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:1002
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5666
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8140
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:4545
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5222
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5269
* 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:161
0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:162
* 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited
0.0.0.0/0 0.0.0.0/0 tcp dpt:6379
0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80
How do i install nodebb on channel file manager!
General Discussion • • Var1

15

0
Votes

15
Posts

2563
Views

A

@Var1 said:

NONE OF THEM WORK 😞 !!!!!!!!!!!

Try reading the documentation.

Note: I believe vps.me requires that you install Ubuntu yourself first. I believe they only support up to 12.04, so you'd need to install the 32 bit version of that, then install NodeBB.
Using nodebb with haproxy as a frontend
General Discussion • haproxy nodebb websockets • • Peter-Zoltan Keresztes

1

0
Votes

1
Posts

679
Views

Hello,

I am trying to setup nodebb with haproxy instead of nginx as frontend. Everything seam to be working however I am getting lots of 403 on /socket.io/ requests.
frontend http-in mode http bind 0.0.0.0:80 redirect scheme https code 301 if !{ ssl_fc } frontend https-in bind 0.0.0.0:443 ssl crt /etc/letsencrypt/live/test/test.pem http-response set-header strict-transport-security "max-age=31536000; includeSubDomains" http-response set-header Content-Security-Policy "default-src 'self' wss: https: *.startech-rd.tk/*; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://code.jquery.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' https://casper.ghost.org/ https://www.gravatar.com/ data:; font-src 'self' https:" http-response set-header X-XSS-Protection "1; mode=block" http-response set-header X-Content-Type-Options "nosniff" http-response set-header Referrer-Policy "no-referrer" reqadd X-Forwarded-Proto:\ https acl is_websocket hdr(Upgrade) -i WebSocket acl is_websocket path_sub -i /socket.io/ use_backend bk_ws if is_websocket acl acl_comments path_beg -i /comments use_backend comments if acl_comments backend comments mode http balance leastconn timeout connect 1s timeout server 600s timeout queue 600s option redispatch retries 3 acl is_woff capture.req.uri -m sub .woff acl is_ttf capture.req.uri -m sub .ttf acl is_eot capture.req.uri -m sub .eot http-response set-header Cache-Control public if is_eot or is_woff or is_ttf http-response set-header Expires -1 if is_eot or is_woff or is_ttf http-response set-header Pragma cache if is_eot or is_woff or is_ttf cookie nodebb insert indirect nocache secure server node1 10.160.125.81:4567 cookie nodebb_node1 check inter 1000 fastinter 500 rise 2 fall 1 server node2 10.160.125.82:4567 cookie nodebb_node2 check inter 1000 fastinter 500 rise 2 fall 1 backend bk_ws option redispatch balance roundrobin option forwardfor option httpclose server node1 10.160.125.81:4567 maxconn 30000 weight 10 cookie ws_node1 check server node2 10.160.125.82:4567 maxconn 30000 weight 10 cookie ws_node2 check```
I have tried to connect directly without haproxy and the websockets are connecting correctly. However I've seen that using the haproxy the websocket protocol changed from wss to https.

Any suggestions on how to fix this?
Nodebb Hosting - Fully Managed - Simple to use
General Discussion • • ChrisPy

6

0
Votes

6
Posts

865
Views

@jaspernl hi there,

We do use vultr for hosting. However, speeds are 10GBPS and you can test the connection speed yourself within the control panel.

Resources are dedicated to each user and not oversold. This hosting is apart of our main brand, Milkk Media Group. We can insure no lag will be found. If you have any loading issues, please let us know, and we will get to work on deploying your own custom server in your location region.