Community

odd nginx behavior

General Discussion

Suggested Topics

  • S

    After installing on Ubuntu, only seeing the "welcome to nginx" page

    General Discussion
    0 Votes
    15 Posts
    829 Views
    dunlixD

    @nubi-kr same

  • B

    Using redis as a cache

    Feature Requests
    0 Votes
    2 Posts
    436 Views
    barisB

    In your setup redis will be used for sessions, pubsub and

    Socket.IO

    favicon

    (socket.io)

     will use it to pass around messages.

    Each nodejs process has it's own post cache, you can see the caches at /admin/advanced/cache.

    Redis pubsub is also used to clear cache on the other nodejs process when it is cleared on one nodejs process. For example when a post is edited it's cache will be cleared on the other nodes.

  • henrywrightH

    How to return a 404 page for a given route?

    Technical Support
    0 Votes
    10 Posts
    3807 Views
    henrywrightH

    @pitaj I did some testing today with /categories 404'd. Seems as though things continued to work fine. I'm not disabling the functionality, just access to the page.

  • markkusM

    Forwarding IPs on nginx proxy

    General Discussion
    0 Votes
    7 Posts
    3660 Views
    A

    @markkus Sounds good to me. 👍 Hopefully this also solves @helltux's issue too.

    Assuming he correctly substitutes his IP in proxy_pass and his domain name in base_url. 😆

  • D

    Nodebb + nginx + varnish problem

    General Discussion
    0 Votes
    5 Posts
    2236 Views
    G

    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

    404 Not Found

    favicon

    (docs.nodebb.org)

     . RHEL 6.5 as well.

Copyright © 2023 NodeBB | Contributors