Feature request - Support host in cterm base path or another option

[dsm1212]

I use a reverse proxy and when i connect through that i dont want to open additional ports. The cterm config assumes i will use a port. That would be dangerous for a terminal interface. All my reverse proxies are fronted buy authelia. So I could add cterm.foo.com and route to that. I suggest if base path starts with http you assume it contains the host. Or add another field for the host.

Maybe it needs to be a separate setting because you need to leave the port off the url being launched.

Thanks

[dsm1212]

I'm not asking for a change on the listen side. A reverse proxy can direct requests to the port. This is just a request for the url used when launching the cterm.

[ryecoaaron]

Since the hostname in the url is resolved by dns, you control that. cterm doesn't care if you put http://name or http://name.domain.com or http://192.168.1.23/. And you can specify a base path now. So, I'm not sure what is needed here?

[dsm1212]

For me, it launches https://《currenturl》: 5000 /《base path.

Thus means I must open port 5000 on my router to reach cterm.

What id like is no port and a different host that I will redirect to the 5000 port. I will put authelia in front of that. I was thinking maybe if base path included the host starting with http you could just skip adding host and port.

[ryecoaaron]

cterm is its own service. It is not using OMV's nginx instance. So, it must listen on a separate port. Change the host in the url doesn't change anything since it is just resolving to your omv system. I guess I could look at adding proxy config to omv's nginx instance but I honestly don't think cterm is something that should be exposed to the internet even with authelia in front of it.

[dsm1212]

I understand, that's why I said I'm not suggesting changing the port. And I can create a cterm.foo.com proxy now to use. It's just putting the port on the launch urls that is really the problem. It doesn't even work on my lan if I log in to omv with a hostnamr url. It only works if I use the lan ip to connect to omv.

[ryecoaaron]

The port is only a problem for your proxy. I don't use a proxy and trying to maintain plugin config for all the different proxies is a pain on my part if even possible in some cases.

If the hostname url doesn't work on your lan, that is a dns/network issue. That said, you can override the hostname (not the port) of the url on the Settings tab. You could even put the IP in there.

[dsm1212]

I’m not sure what you mean. I have a domain for my address. It works fine but it is a hairpin route through my router which properly only passes the ports I have open. I can locally define a name on my routers dns config using my lan port. Neither will help me outside the lab. Honestly it’s ok though. I can route a name through the proxy to the cterm login page. It’s just the client links on the omv ui that assume the server config should be assessible from the url to omv and that’s a bad assumption. You can close this.

[ryecoaaron]

It’s just the client links on the omv ui that assume the server config should be assessible from the url to omv and that’s a bad assumption.

It is not a bad assumption. It is using the link that the server is creating. Your proxy is outside of that and translating the url. The plugin knows nothing about that. I allow the hostname to be overridden but unless I create a proxy with the plugin itself, I can't get rid of the port.

I will leave this open but someone else will have to contribute the change.