ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Looks like your connection to NodeBB was lost, please wait while we try to reconnect.

    IT Discussion
    1
    5
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Emad RE
      Emad R
      last edited by Emad R

      I am having this issue with my self hosted NodeBB any insight here that can help me ?

      Fresh Install using Nginx as proxy

      Emad RE 3 Replies Last reply Reply Quote 0
      • Emad RE
        Emad R @Emad R
        last edited by Emad R

        @emad-r

        Solved seem was related to npm app I installed but didnt understand what it will do, its called forever and you can , it was duplicating the NodeBB service.

        I removed it and rebooted the server and the npm log seems correct:

        [deprecated] `String.prototype.rtrim` is deprecated as of NodeBB v1.5; use `utils.rtrim` instead.
           5/9 00:15:31 [1294] - info: [socket.io] Restricting access to origin: http://192.168.1.39:
           5/9 00:15:31 [1294] - warn: [plugins/load] The following plugins may not be compatible with your version of 
           NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
           nodebb-plugin-markdown
        
        5/9 00:15:31 [1294] - info: Routes added
        5/9 00:15:31 [1294] - info: NodeBB Ready
        5/9 00:15:31 [1294] - info: Enabling 'trust proxy'
        5/9 00:15:31 [1294] - info: NodeBB is now listening on: 0.0.0.0:4567
        
        
        1 Reply Last reply Reply Quote 1
        • Emad RE
          Emad R @Emad R
          last edited by

          @emad-r
          config.json
          {
          "url": "http://localhost:4567",
          "secret": "secret",
          "database": "redis",
          "redis": {
          "host": "127.0.0.1",
          "port": "6379",
          "password": "",
          "database": "0"
          }
          }

          1 Reply Last reply Reply Quote 0
          • Emad RE
            Emad R
            last edited by

            nginx:

            location / {
            proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;
            
                proxy_pass http://127.0.0.1:4567;
                proxy_redirect off;
            
                # Socket.IO Support
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
            }
            
            1 Reply Last reply Reply Quote 0
            • Emad RE
              Emad R @Emad R
              last edited by

              @emad-r

              Getting this in npm logs:

              5/9 00:09:48 [16766] - info: Routes added
              5/9 00:09:48 [16766] - info: NodeBB Ready
              5/9 00:09:48 [16766] - info: Enabling 'trust proxy'
              5/9 00:09:48 [16766] - error: Error: listen EADDRINUSE 0.0.0.0:4567
              at Object.exports._errnoException (util.js:1020:11)
              at exports._exceptionWithHostPort (util.js:1043:20)
              at Server._listen2 (net.js:1258:14)
              at listen (net.js:1294:10)
              at net.js:1404:9
              at _combinedTickCallback (internal/process/next_tick.js:83:11)
              at process._tickCallback (internal/process/next_tick.js:104:9)
              5/9 00:09:48 [16766] - error: NodeBB address in use, exiting...
              3 restarts in 10 seconds, most likely an error on startup. Halting.

              1 Reply Last reply Reply Quote 0
              • Emad RE
                Emad R @Emad R
                last edited by Emad R

                @emad-r

                Solved seem was related to npm app I installed but didnt understand what it will do, its called forever and you can , it was duplicating the NodeBB service.

                I removed it and rebooted the server and the npm log seems correct:

                [deprecated] `String.prototype.rtrim` is deprecated as of NodeBB v1.5; use `utils.rtrim` instead.
                   5/9 00:15:31 [1294] - info: [socket.io] Restricting access to origin: http://192.168.1.39:
                   5/9 00:15:31 [1294] - warn: [plugins/load] The following plugins may not be compatible with your version of 
                   NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
                   nodebb-plugin-markdown
                
                5/9 00:15:31 [1294] - info: Routes added
                5/9 00:15:31 [1294] - info: NodeBB Ready
                5/9 00:15:31 [1294] - info: Enabling 'trust proxy'
                5/9 00:15:31 [1294] - info: NodeBB is now listening on: 0.0.0.0:4567
                
                
                1 Reply Last reply Reply Quote 1
                • 1 / 1
                • First post
                  Last post