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

    NodeBB 1.10.2 Fresh Install Errors

    IT Discussion
    nodebb nodebb 1.10.2 nginx centos centos 7 linux socket.io
    2
    4
    577
    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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Getting several of these errors on a clean install, also socket.io appears to be failing (maybe totally unrelated.)

      Source map error: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
      Resource URL: https://site.com/assets/src/client/chats/recent.js?v=qa1m9mg8rig
      Source Map URL: public/src/client/chats/recent.js.map[Learn More]
      

      First time that I've seen this. Brand new install, behind NGinx. On CentOS 7.

      1 Reply Last reply Reply Quote 0
      • A
        Alex Sage
        last edited by

        Try this:

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        

        From @JaredBusch's guide.

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @Alex Sage
          last edited by

          @aaronstuder said in NodeBB 1.10.2 Fresh Install Errors:

          Try this:

          # Socket.IO Support
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "upgrade";
          

          From @JaredBusch's guide.

          That's already there. From what I can tell, the Nginx config (which is what you are showing) and the NodeBB config.json are identical to working system.s

          1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller
            last edited by

            Sorry, ignore me. I got this figured out. I was being really dumb and had the wrong config.json file open and didn't know what I was looking at. Just ignore. Yes, the socket.io settings were missing, but were on my screen so I was sure that they were there.

            1 Reply Last reply Reply Quote 2
            • 1 / 1
            • First post
              Last post