Runnig forum without :4567 port in the URL

[xpcontact]

Hi,
I am testing nodebb @ www.w9forum.com , I got a problem that I need always to add the port 4567 in the end in order to get access...
How to fix this? because visitors should only type the url without the port.
Thank you guys!

[Henrock]

You can use Nginx as a reverse proxy in front of Node: https://github.com/designcreateplay/NodeBB/wiki/Configuring-nginx-as-a-proxy-to-NodeBB

[xpcontact]

Perfect solution if I had nginx, but I have apache

[Henrock]

Sorry, I don't know how to do it with Apache. Maybe switch to Nginx.

[xpcontact]

was reading if I could buy another IP, and install nginx on it. along with apache.

[xCausxn]

You need to use nginx, you can however link nginx and apache: using this tutorial

https://www.digitalocean.com/community/articles/how-to-configure-nginx-as-a-front-end-proxy-for-apache

and

https://github.com/designcreateplay/NodeBB/wiki/Configuring-nginx-as-a-proxy-to-NodeBB

@xpcontact

[Scuzz]

@xCausxn Isnt a reverse proxy available on apache?

[finid]

I think there's an issue that needs to be fixed in NodeBB, because if, during installation, you specify that a port not be used, it still uses a port anyway.

[julian]

if, during installation, you specify that a port not be used, it still uses a port anyway.

Working as Intended

All internet facing software uses ports. The proxy just hides it.

[finid]

@julian

But if that's the case, why are we asked during installation whether a port should be used for the connection or not. And if the answer is n, that answer is reflected in config.json, but the port is still used anyway.

[julian]

It is used to instruct NodeBB to omit the port in any URLs that are shown to the end user. For example, if you hover over any of the links on this site, you'll see that they point to "community.nodebb.org", as use_port is false. If it were true, it would be community.nodebb.org:4567.

NodeBB always listens on a port, the proxy hides it, so a friendlier URL can be used (the proxy forwards requests from port 80 (portless) to port 4567, hence proxying requests to NodeBB).

[buynsellcloudcom]

@julian how would you use the
changed "use_port": true to "use_port": false

"base_url": "https://mydomain.com"

config.json

{
    "url": "http://localhost:4567",
    "secret": "xxxxxxxxxxxxxxx",
    "database": "redis",
    "redis": {
        "host": "127.0.0.1",
        "port": "6379",
        "password": "",
        "database": "0"
    }
}

thanks

[scottalanmiller]

@xpcontact said in Runnig forum without :4567 port in the URL:

Hi,
I am testing nodebb @ www.w9forum.com , I got a problem that I need always to add the port 4567 in the end in order to get access...
How to fix this? because visitors should only type the url without the port.
Thank you guys!

You can set the port to whatever you want. But that's not a good idea.

The idea behind any system like this on unknown ports is that you are expected to:

1. Have a reverse proxy in front of it.
2. Translate to SSL / Port 443 in the proxy.

[scottalanmiller]

@xpcontact said in Runnig forum without :4567 port in the URL:

Perfect solution if I had nginx, but I have apache

You install it. Having Apache or not should not matter.

It's like needing a hammer. Just because you own a wrench doesn't preclude you from grabbing a hammer when needed.

[scottalanmiller]

@Scuzz said in Runnig forum without :4567 port in the URL:

@xCausxn Isnt a reverse proxy available on apache?

Yes, but it is a lot harder and doesn't work as well.

[scottalanmiller]

@finid said in Runnig forum without :4567 port in the URL:

@julian

But if that's the case, why are we asked during installation whether a port should be used for the connection or not. And if the answer is n, that answer is reflected in config.json, but the port is still used anyway.

Just part of how all the pieces come together.