Nginx custom proxy (feature request)

[vontainment]

It would be nice if in the GUI for domains could select and option to just run a Nginx Proxy. No apache virtual host made, no php, and with an option to specify and ip-port combo. Currently to do this, I've had to just create a blank apache file and hard write the IP and port in a tpl and stpl files.

[ManuelReschke]

Just install only nginx and create a custom template for that. Done

[theotherpeople]

I agree. It is useful for playing with docker or LXC.

[vontainment]

Yes but if you are hosting a site with apache-nginx and you have an external or internal service you want to proxy this would be convenient.

[vontainment]

Basically you just need a no apache option and a field to set the templates IP variable

[jaapmarcus]

Also to combine with...

https://forum.hestiacp.com/t/redirect-url-of-a-domain/2315/3

[vontainment]

It also need the option to change the port number. To be able to set the IP and port for both HTTP and https. Only because sometimes you don't have the option of both when proxying something. And so you have to proxy to Port 80 under the https template. And then you basically have SSL termination

[jaapmarcus]

Probally need have multiple options:

1. Same server different port -> NodeJS for example
2. SSL termination
3. Different server same ports / different ports
4. 302 / 301 redirect

Al options are possible only a lot of work to implement them al...

[vontainment]

It should be basic. That's what templates are fore. Asking as we can set the IP and port used in the templates proxy section we could create reusable templates. I regularly set up proxies for the same 10 services for clients. So in situations like that it be nice. Or ppl can share templates and you can set it for your up situation

[vontainment]

Probally need have multiple options:

1. Same server different port -> NodeJS for example
2. SSL termination
3. Different server same ports / different ports
4. 302 / 301 redirect

Al options are possible only a lot of work to implement them al...

SSL Termination should not be needed. If Nginx is set for ssl but the connecting server is not or is set to connect by http it will terminate itself. Or maybe just a custom conf option like you checkmark the box and hestia creates a default template that you can then edit like the system configs do.

[Kudja]

Agree, nice to have future for different cases

• docker
• nodejs
• java app's
  ...

Related to options 1 and 3 can be added just as text field and then user able to put here direct string like http://domain.com:8090/ as example

[xeruf]

templates have a port variable, but I don't know how it's supposed to be set?
https://docs.hestiacp.com/admin_docs/web.html#available-variables

[jaapmarcus]

Those are for nginx port server. You really don't want to change that...

We need to add an custom port and it should be quite easy. How ever we need to find a beter way so we can implement new "features" easier in the future

[liamgibbins]

This would be an owesome option to have, I have my cctv, nextcloud and my solarpv monitoring server all on different ports, this would make it so much easier for people wanting to use this already awesome panel either private like me or commercial like others do.

[Scan4u]

Just found this topic - and totally agree with this feature request.
I have the running Hestia server with home webpage (Apache+nginx + Lets encrypt SSL + HTTPS redirection and HSTS enabled).
Additionally running a few Docker images.. And it is a big problem to get those docker images to work with enabled HSTS on https. Got the error. For example - here is a result for Rapid Dashboard on Docker - it use the default port 9660:

[0spinboson]

would also love to have this.

[MajorTomDE]

I also look forward to have an direct configuration of ports in hestiaCP GUI. This would make configuration, eg with docker containers, so much easier.

[liamgibbins]

I am currently running nginx proxy manager infront of hestiacp, it would be awesome to have this feature built in to hestiacp

[MajorTomDE]

The greatest solution would be to have the options like in Nginx Proxy Manager. So Hestia should provide besides the classic forwarding options for domains und subdomains also the possibility to configure a port target + SSL certificate.

So we can easly configure e.g. docker apps.

[djlongy]

I am currently running nginx proxy manager infront of hestiacp, it would be awesome to have this feature built in to hestiacp

Are you running NPM on the same box as hestiacp and intercepting all 443 traffic? Or an entirely different machine in front of it?

[liamgibbins]

I am running it on a different vm porting all traffic to it from my router since its all installed on my homelab. I don't run hestiacp for profit just to host my own websites and brought them onto my home setup to try save some money as things funds are getting very tight. This helps me to keep my monthly donation to hestiacp live Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: djlongy ***@***.***> Sent: Tuesday, October 25, 2022 6:40:52 AM To: hestiacp/hestiacp ***@***.***> Cc: liamgibbins ***@***.***>; Comment ***@***.***> Subject: Re: [hestiacp/hestiacp] Nginx custom proxy (feature request) (#1453) I am currently running nginx proxy manager infront of hestiacp, it would be awesome to have this feature built in to hestiacp Are you running NPM on the same box as hestiacp and intercepting all 443 traffic? Or an entirely different machine in front of it? — Reply to this email directly, view it on GitHub<#1453 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD4OWLFOYAMUIHWXUMF5MXDWE5XGJANCNFSM4UWLHEGA>. You are receiving this because you commented.Message ID: ***@***.***>

[davidspring]

I too would like this feature for the reasons explained in issue 1997 – which is a duplicate of this issue 1453.

[Asellsus]

At the moment i'm exactly at the point where i need this feature. I really don't know how to forward a created domain to ip:port

[jaapmarcus]

I am working on a feature request for it:

[xeruf]

If we all need it, maybe it's time to compile a bountysource :)

As a temporary workaround I copied the default templates to a template with the port and edited the proxy port by hand in the templates, making it at least reusable for services running on the same ports.

[MajorTomDE]

@jaapmarcus That would be great. Making docker apps running as subdomain (mydomain.com:1234 >>> app1.mydomain.com) is currently my biggest pain point with HestiaCP.
Sure, templates are possible but sometimes it’s so complicated. A web interface like nginx proxy manager would be great.

[dan-atyp]

This would be an extremely useful feature.
To be able to forward to an arbitrary IP and port with NGINX and to utilise Hestia's existing SSL features would be excellent.

[Finallf]

Another one who arrived at the time of needing something like this, I come from ISPconfig and Sentora, where I used NPM in front of them.
As I changed my entire web stack from ISPConfig/Sentora to HestiaCP, it would be wonderful to have something to not need to use NPM, since HestiaCP already has NGINX, I believe you can do something like NPM.

[howard868]

I also need this feature.