Categories

• Announcements

  Check here for announcements about NodeBB

  61
  Topics
  816
  Posts

  D

  Question - am I supposed to see the existing comments at the bottom of a post or just the text field and submission button/links that lead me to the Nodebb topic? There's a DIV in place, it looks like, but it's empty.
• General Discussion

  A place to talk about whatever you want

  2861
  Topics
  18625
  Posts

  

  at the moment I need to add users to group individually one by one, and I have to remember their usernames to type into suggestive box. Instead is there a way to add multiple users in one go by selecting checkboxes or something?
• NodeBB Development

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

  NodeBB Blog

  Feature Requests

  Bug Reports

  NodeBB Localization
  2719
  Topics
  16738
  Posts

  N

  @faizanzahid said in Private messaging: Is there anyway for mods or admin to read the user's private messages? Would also be interested in this as we may need to moderate user's interactions when they are behaving poorly toward one another.
• NodeBB Plugins

  Discussion regarding NodeBB Plugin development.

  Plugin Development

  Plugin Requests
  1321
  Topics
  11437
  Posts

  

  @c3do it's just a warning. You can ignore it. Are you having any actual issues with the functionality of the plugin?
• NodeBB Themes

  A public listing of community themes created by the NodeBB community.
  326
  Topics
  2658
  Posts

  

  @Nicolas-0 This is a recent topic and form stats (widget)
• Technical Support

  Need help with installing or configuring NodeBB? Look here.

  Swedish Support (Unofficial)

  Polish Support
  2576
  Topics
  14206
  Posts

  S

  I recently upgraded from nodejs 9.10.1 to 10.15.0, and the problem has come back ERROR Something went wrong while parsing server response [Error] Failed to load resource: the server responded with a status of 502 () (upload, line 0) https://support.sweetpproductions.com/api/post/upload
• 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.11.0 has been released!
  Hi folks, This is just a minor release. For the issues solved, please check our GitHub page. Cheers.
• Version 1.12.0 Breaking Changes
  If you have any plugins using any of those hooks/methods, please upgrade your plugin and add …