Buy Hosting

After 6+ Years

General Discussion

Suggested Topics

  • JenklerJ

    Marry christmas and a Happy new year!

    General Discussion
    3
    0 Votes
    3 Posts
    1k Views
    MJM

    Best wishes to everyone 🙂

  • D

    nodebb 1.6.1 on heroku

    General Discussion
    3
    0 Votes
    3 Posts
    1k Views
    D

    I was able to get around it by pushing all files to heroku git instead of mentioned files in documentations

    So, instead of,

    git add -f Procfile config.json package.json build && git commit -am "adding Procfile and configs for Heroku"

    I did,
    git add . && git commit -am "adding Procfile and configs for Heroku"

    This solved my problem.

    However, I have moved away from Heroku and deployed my forum on GCP.

  • MJM

    Adult content not viewable for users who are below 18 years old

    General Discussion
    5
    1 Votes
    5 Posts
    1k Views
    MJM

    @pichalite okay

    @pichalite @PitaJ Thanks you for reply 🙂

  • lombisiL

    0.6.1 - 0.7.0

    General Discussion
    11
    0 Votes
    11 Posts
    3k Views
    lombisiL

    npm install -g n # Install n globally
    n 0.10.33 # Install and use v0.10.33

    $ git fetch
    $ git checkout v0.7.x
    $ git merge origin/v0.7.x

    ./nodebb upgrade

    It was dissolved

  • R

    upgrade to 0.6.x issue

    General Discussion
    15
    0 Votes
    15 Posts
    9k Views
    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)
Copyright © 2023 NodeBB | Contributors