NodeBB is currently sitting at 9,999 commits...

General Discussion

Suggested Topics


  • 0 Votes
    1 Posts
    169 Views

    Hi,

    In settings I have session time set for 14 days.
    But many users have a problem that they are being logged out every day.
    I also need to log in every single day.

    Where I can look for the issue ?

  • 0 Votes
    5 Posts
    714 Views

    Tested it now for some days, It works great! Wonderful to save some time 😉

  • NodeBB and Ghost

    General Discussion
    0 Votes
    13 Posts
    8k Views

    @ogerly said:

    there is information about the merger of nodebb and ghost ?

    Not merging, but can be used with each other.

  • 0 Votes
    5 Posts
    2k Views

    My knowledge of Varnish is very limited - but don't you have to either pipe Varnish into nginx and then NodeBB or nginx into Varnish and then NodeBB? From your configuration, it seems you're trying to pipe nginx into NodeBB on port 2000 and the same for Varnish. Can Varnish and nginx coexist on the same port?

    Here is my working configuration but against, I'm running nginx to Varnish's default port (e.g., 6081).

    server { listen 80; server_name domain.com *.domain.com; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:6081/; #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"; } }

    For Varnish, I'm just using the default instructions. RHEL 6.5 as well.

  • 1 Votes
    4 Posts
    2k Views

    Oh probably 301 is better, since it teaches Google to use the new one instead, but remember what happened last time we tried a 301? NodeBB.org ended up not ranking for months 😄