Community

upgrade to 0.6.x issue

General Discussion
  • R

    Upgraded my 0.5.7 nodebb today to 0.6.x and getting this error always;

    WebSocket connection to 'ws://www.koinyum.com/socket.io/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 503

    WebSocket connection to 'ws://www.koinyum.com/socket.io/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 400

    The error keeps triggering..

    @update i'm also using apache.

    0
  • barisB

    See https://github.com/NodeBB/NodeBB/issues/2554

    0
  • P

    I was having the same issue as OP with websockets, now I have this in console at ACP.

    GET https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419539326381-93&sid=TEguvhP5GP2nhwDABM 400 (Bad Request)
nodebb.min.js:12667
POST https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419539337195-94&sid=TEguvhP5GP2nhwDABM 400 (Bad Request)

    Using apache, ssl, one instance of nodebb.

    0
  • R

    same with @priapo, didn't fixed for me.

    https://github.com/NodeBB/NodeBB/issues/2554#issuecomment-68113125

    0
  • julianJ

    Just a thought... what happens when you run npm ls socket.io socket.io-client?

    For me:

    [email protected] /home/julian/Projects/nodebb/forum
├── [email protected] 
└── [email protected]
    0
  • wzrdtalesW 
    [email protected] /home/nodebb/nodebb
├── [email protected] 
└── [email protected]

    As mentoined in the issue, the polling and so the transfer works but throws errors if you're idling and no data is transferred while the long polling request.

    0
  • P

    @julian said:

    npm ls socket.io socket.io-client

    [email protected] /home/user/bbs
├── [email protected] 
└── [email protected]
    0
  • julianJ

    Are you also up to date with vanilla and lavender? This could be caused by the loading of an old library (v0.9.x) instead of the newest (v1.0.0).

    @priapo I can't access your NodeBB right now to check.

    0
  • P

    I reinstalled both.. still getting the error... maybe is something with Apache proxy as @raistlinthewiz said he is also using it.

     GET https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419631909437-6&sid=0GXmkhgSRxZlCDESAAAW 400 (Bad Request)
nodebb.min.js:12667
POST https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419631920915-7&sid=0GXmkhgSRxZlCDESAAAW 400 (Bad Request)
nodebb.min.js:12667
GET https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419631925604-14&sid=9ndsEWRLlGKLAhb5AAAX 400 (Bad Request)
nodebb.min.js:12667
POST https://bbs.kassius.org/socket.io/?EIO=3&transport=polling&t=1419631937170-15&sid=9ndsEWRLlGKLAhb5AAAX 400 (Bad Request)
    0
  • julianJ

    @priapo Caching layer in front of the web server? (varnish etc)

    Possibly browser cache?

    0
  • P

    No nothing.. I tried installing nginx and used it with the first setup in here, no ssl: https://docs.nodebb.org/en/latest/configuring/proxies/nginx.html still the same. I created another chrome user because of the 301 redirects to https so no cache. Websockets dont work (loading icon stays) and polling throws errors, but at least works...

    my config is

    {
    "url": "https://bbs.kassius.org",
    "port": "4454",
    "secret": "xxsecret",
    "bind_address": "127.0.0.1",
    "database": "redis",
    "redis": {
        "host": "127.0.0.1",
        "port": "4562",
        "password": "verylongredispass",
        "database": "0"
    },
    "bcrypt_rounds": 12,
    "upload_path": "/public/uploads",
    "use_port": false,
    "socket.io": {
        "transports": ["polling","websocket"]
    }
}
    0
  • P

    Now it is working for me, it was really something with the proxy on Apache 2.4 and socket.io1.0, I saw this topic:

    And configured Apache like this:

    Without SSL

    https://gist.github.com/kassius/78c633a803d3c711b171

    <VirtualHost *:80>
 
	ServerName forum.example.com
 
#	ServerAdmin [email protected]
 
	<Proxy *>
		Require all granted
	</Proxy>
 
	ProxyRequests off
	ProxyVia on
 
	RewriteEngine On
	RewriteCond %{REQUEST_URI}  ^/socket.io            [NC]
	RewriteCond %{QUERY_STRING} transport=websocket    [NC]
	RewriteRule /(.*)           ws://localhost:4567/$1 [P,L]
 
	ProxyPass        /socket.io http://localhost:4567/socket.io
	ProxyPassReverse /socket.io http://localhost:4567/socket.io
 
	<Location />
		ProxyPass http://127.0.0.1:4567/
		ProxyPassReverse http://127.0.0.1:4567/
	</Location>
 
	ErrorLog /home/username/logs/apache/forum-error.log
	CustomLog /home/username/logs/apache/forum-access.log combined
 
</VirtualHost>

    With SSL, redirecting to HTTPS:

    https://gist.github.com/kassius/954e0787d6893c5ab8e1

    <VirtualHost *:80>
 
	ServerName forum.example.com
	Redirect permanent / https://forum.example.com
 
</VirtualHost>
 
<VirtualHost *:443>
 
	ServerName forum.example.com
 
	SSLEngine on                                                                
	SSLProtocol all -SSLv2                                                      
	SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM                
 
	SSLCertificateFile /etc/apache2/ssl/example-com/forum.ssl.crt                           
	SSLCertificateKeyFile /etc/apache2/ssl/example-com/private.key                        
	SSLCertificateChainFile /etc/apache2/ssl/example-com/sub.class1.server.ca.pem 
 
#	ServerAdmin [email protected]
 
	<Proxy *>
		Require all granted
	</Proxy>
 
	ProxyRequests off
	ProxyVia on
 
	RewriteEngine On
	RewriteCond %{REQUEST_URI}  ^/socket.io            [NC]
	RewriteCond %{QUERY_STRING} transport=websocket    [NC]
	RewriteRule /(.*)           ws://localhost:4567/$1 [P,L]
 
	ProxyPass        /socket.io http://localhost:4567/socket.io
	ProxyPassReverse /socket.io http://localhost:4567/socket.io
 
	<Location />
		ProxyPass http://127.0.0.1:4567/
		ProxyPassReverse http://127.0.0.1:4567/
	</Location>
 
	ErrorLog /home/username/logs/apache/forum-error.log
	CustomLog /home/username/logs/apache/forum-access.log combined
 
</VirtualHost>

    Now is working even with pure websockets like "transports": ["websocket"].
    It uses Apache's mod_rewrite module.

    0
  • julianJ

    @priapo Keep in mind putting a socket.io section in config.json doesn't do anything 😄

    Edit: I stand corrected 😄

    wzrdtalesW 1 Reply
    0
  • P

    The setting in config.json doesn't affect nodebb? I think it does, see I changed config.json between "transports": ["websocket","polling"] and "transports": ["polling","websocket"] and saw by Chrome Inspector that with websocket as prefered method it doesn't uses polling.

    Using "transports": ["polling","websocket"]:

    polling

    Using "transports": ["websocket","polling"]:

    websocket

    I see this https://github.com/NodeBB/NodeBB/commit/e0edb71a8ab2f23eaebf5c7557d5d1d19bb55baa

    0
  • wzrdtalesW

    @julian said:

    @priapo Keep in mind putting a socket.io section in config.json doesn't do anything 😄

    We had just talked about this configuration option short time ago in the issue 😄 so obviously it does affect. But "transports": ["polling","websocket"] is now the Standard.

    @priapo if you can't use the websockets you can set also "transports": ["polling"], then you will only get the failures for the long polling request which throws errors.

    I just tested by connecting directly without any proxy before NodeBB. The timeout disappears.

    So one failure source is that the timeout is higher than what is allowed by the proxy e.g. cloudflare. So an option to adjust the timeout would be great!

    The failure throwing which are left now are:

     GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766084670-12&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request)
nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766094756-13&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request)
nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766096635-23&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request)
nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766106720-24&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request)
nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766108697-34&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request)
nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766118775-35&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request)
nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766120692-45&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)
nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766130783-46&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)
    0

Suggested Topics

  • M

    Help NodeBB doesn't work after upgrade to 1.3.0

    Solved General Discussion
    0 Votes
    26 Posts
    6574 Views
    M

    @PitaJ said in Help NodeBB doesn't work after upgrade to 1.3.0:

    i love you bro 😄

  • K

    revert from 0.6.1 to 0.6.0

    General Discussion
    1 Votes
    3 Posts
    1987 Views
    K

    @a_5mith said:

    git checkout v0.6.x
    git pull
    ./nodebb upgrade

    that worked. let me backup and then check out the master.

  • R

    Invalid CSRF token

    NodeBB Development
    0 Votes
    8 Posts
    6058 Views
    mootzvilleM

    I figured out my issue...

    MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

  • julianJ

    Plugin Developers!! Read this re: v0.6.0 Breaking changes

    NodeBB Development
    2 Votes
    17 Posts
    6570 Views
    julianJ

    I correctly assumed (and this has been validated through actual plugin upgrades) that the latest hash in npm points to the most recently published version, and not the highest version.

    That is, given your plugin nodebb-plugin-example

    If v1.0.0 is compatible with v0.5.4 If v1.1.0 is compatible only with v0.6.0 The latter is published first A user typing npm install nodebb-plugin-example will receive v1.0.0 of the plugin, irrespective of what NodeBB version he/she is running, even though v1.1.0 is technically newer

    Now, special note: The NodeBB Package Manager doesn't do this. When the ACP calls nbbpm to request a suggested package, we query npm for the plugin data, and sort the versions before checking compatibility, so this issue is moot.

  • meetdilipM

    How to upgrade from 0.4.1 to 0.4.2

    General Discussion
    1 Votes
    8 Posts
    2025 Views
    psychobunnyP

    In general plugins should be compatible within a minor version (ex. 0.4 to 0.5), at least from now on 🙂 We are doing deprecation notices so you will know in advanced what plugins will break when you upgrade.

Copyright © 2023 NodeBB | Contributors