Community

How to configure nginx to proxy to 4567

Technical Support

Suggested Topics

  • T

    pidfile not found nginx

    Unsolved Technical Support
    0 Votes
    4 Posts
    42 Views

    julianJ

    Not really, no... It just means that you might have a running NodeBB instance you can't stop (short of running something like kill)

  • H.urnaH

    SSO Authentication - Https - NGINX configuration

    Technical Support
    0 Votes
    2 Posts
    208 Views

    H.urnaH

    Finally found a topic with good explanation an answers:

    Didn't expect the config.json would influence such requests.

    Kind regards.

  • D

    Websocket error with NodeBB running through a proxy server

    Technical Support
    0 Votes
    2 Posts
    502 Views

    D

    To resolve this, I changed the Proxy module I was using. It uses less code to implement and works with websockets. I think the NodeBB Node.js proxy documentation is out of date so I'll be submitting a PR with the new method I found.

    Working code is as follows:

    /** * Proxy forum */ const proxy = require('http-proxy-middleware'); // Forum Proxy app.use( '/forum', proxy({ target: 'http://www.myforum.co.uk/forum', changeOrigin: true, ws: true, }) );

    Another potential GOTCHA here is that this Prixy setup needs to be declared ABOVE the 'body-parser' module (if it's being used). The wrong order will prevent post requests from being proxied.

  • S

    Mandrill Confirmation Link Not Including :4567?

    Technical Support
    0 Votes
    6 Posts
    1532 Views

    S

    Thanks @baris that did the trick

  • KingCatK

    400 and 522 errors since enabling SSL via Nginx proxy

    Technical Support
    1 Votes
    14 Posts
    10028 Views

    KingCatK

    Welp, I solved it.

    Turns out I had the wrong directory specified in nginx for static assets. It was pointing to a different install of nodebb. For some reason that caused issues with socket.io (and only with safari/opera for some reason).

    Now, here's the weird thing. I only recently started using nginx to serve the assets. Recently as in like this morning. Before that I simply had a proxy pass setup and let nodebb serve the assets. I'm not sure what was causing the 400/502 errors then but I'm just glad their solved now.

| | | |
Copyright © 2023 NodeBB | Contributors