Categories

• Announcements

  Check here for announcements about NodeBB

  61
  Topics
  814
  Posts

  F

  Amazing work guys! happy to see improvements, loved the dropdown autosuggest on categories, i'd love if you guys also add same auto suggest when we are using the global search to search through topics, it will be a huge UX improvement for forums with so many topics. it should auto suggest only topic titles for now atleast. Great work!
• General Discussion

  A place to talk about whatever you want

  2842
  Topics
  18551
  Posts

  F

  @Koshy246 哦 Mr 你在
• NodeBB Development

  Stay tuned here to hear more about new releases and features of NodeBB!

  NodeBB Blog

  Feature Requests

  Bug Reports

  NodeBB Localization
  2700
  Topics
  16665
  Posts

  T

  @baris https://github.com/NodeBB/NodeBB/issues/7120 tom-rade created this issue in NodeBB/NodeBB open Group admins don't recieve email notifications when users send a request to join a group #7120
• NodeBB Plugins

  Discussion regarding NodeBB Plugin development.

  Plugin Development

  Plugin Requests
  1297
  Topics
  11295
  Posts

  

  Seems the link thats supposed to appear under Plugins in the ACP is not there.
• NodeBB Themes

  A public listing of community themes created by the NodeBB community.
  324
  Topics
  2617
  Posts

  

  Update to 3.0.13, install last version npm install nodebb-theme-oxide@latest or ./nodebb upgrade Changelog: Github - Commits Add tid settings, Enhanced composer-deafult and quick-reply, and more small fixes
• Technical Support

  Need help with installing or configuring NodeBB? Look here.

  Swedish Support (Unofficial)

  Polish Support
  2527
  Topics
  13944
  Posts

  N

  Up to now the URL was set to "https://forum.site.de" and produced no problems. I tried "/" and "https://127.0.0.1:4567". The described problem stays. The only effect is, socket.io can't connect. So it seems my original setting can't be that wrong.
• Tutorials

  NodeBB guides, how-to's and general tips and tricks

  43
  Topics
  301
  Posts

  

  This FAQ is applicable for the following situations: You're receiving the following error in the Javascript console: WebSocket connection to 'wss://<site>/socket.io/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 400 The "Looks like your connection to NodeBB was lost, please wait while we try to reconnect." alert box and the spinner in the navbar consistently appear You want your users to be able to access NodeBB from multiple subdomains on your site Background By default, NodeBB only allows websocket connections from the "url" value in config.json. This is because of what is called Cross-Site Websocket Hijacking. By restricting the origin at which sockets can connect, we prevent this attack from taking place. Diagnosis To make sure that your issue is in fact caused by an origin mismatch, try this: Stop the NodeBB server: ./nodebb stop Start NodeBB in dev mode: ./nodebb dev Visit your site, and see if the issue is resolved. Ctrl+C to exit dev mode If the issue disappeared when visiting your site running in dev mode, then your problem is in fact an origin mismatch. If not, it is likely something else, so look around or ask a question here on the forum. Solutions The easiest solution is to set the "url" value in config.json to exactly the URL at which you access your NodeBB forum. For instance, the configuration for this site is { "url": "https://community.nodebb.org", ... } If you want your forum to work from multiple origins (like www.yoursite.com and yoursite.com) the preferred option is to just redirect one to the other. For instance, redirect www.yoursite.com to yoursite.com within your reverse proxy. If you absolutely must have full access from multiple origins, you can configure the accepted origins directly. As documented here, you can add a socket.io:origins property to config.json. For example, to allow accessing the forum sockets from the main NodeBB site, nodebb.org, the following would be added to our config: { ... "socket.io": { "origins": "https://community.nodebb.org:* https://nodebb.org:*" } } Make sure your original site is included in the new origins property, and that you add :*, otherwise it's invalid. Still having issues? It's likely a reverse proxy configuration issue. Take a look at the proxy documentation for examples. If you still have issues, ask a question here on the forum.

• NodeBB v1.10.2 has been released!
  Hi folks, This is just a minor release. For the issues solved, please check our GitHub page. Cheers.
• Version 1.11.0 Breaking Changes
  If you have any plugins using any of those hooks/methods, please upgrade your plugin and add …