Hestia Edge Case

Stage4000

I am running FOSSbilling and Hestia, I have Hestia routed through a cloudflare tunnel and FOSSbilling can talk to it fine and all that despite it no longer having the 8083 port, but it still tries to send users to :8083 when clicking the button, if I change the port for hestia in FOSSbilling to 443 the button works but the API doesn't (which, I can't really explain tbh).

Stage4000

I just edited the template to manually set the panel address.

jaapmarcus

Stage4000 You should be able set ip addr for Fossbilling and it should be working. Proxying the api causes some unexpected things mainly the mainly the fact the changing ip addr from the Cloudflare node…

BelleNottelling

That's.. odd?
I thought HestiaCP used the same port for it's API & interface?
Are you using a custom config for HestiaCP?

But furthermore, why route everything through a Cloudflare tunnel? That's an unorthodox and arguably sub-optimal way to configure and use a web-server.

jaapmarcus

BelleNottelling Because:

https://github.com/FOSSBilling/FOSSBilling/blob/ffdf9e057967cff302011ec0929cf41f7e81938e/src/library/Server/Manager/Hestia.php#L63-L66

So if you have a custom setup were you proxy every traffic from hostname it will use port number.

I don't know if there is an easy fix for it except make it an option…