Hestiacp control panel is accessable with all hosted website:port

vk10604 · April 17, 2023, 9:06pm

I host my cp at 1.2.3.4:2083 and have pointed my domain, hestiacp.example.com, to that ip. I am sucessfully able to access the control panel via hestiacp.example. tld:2083. The funny part now comes. I’ve used hestiacp to host three websites, including qwerty.com, xyz.com, and abc.com. When I try to access abc.com, the related website opens without a problem, but when I try to access abc.com:2083, the control panel website loads instead. The other websites are experiencing the same issue. how can this be stopped from happening?

eris · April 18, 2023, 5:42am

There is currently no way to disable it.

It is because as Hestia is currently run as a service on port 8083

Option would be create a template with Nginx

github.com

jaapmarcus/web-templates/blob/master/templates/nginx/cp.stpl

#=======================================================================#
# Default Web Domain Template                                           #
# DO NOT MODIFY THIS FILE! CHANGES WILL BE LOST WHEN REBUILDING DOMAINS #
#=======================================================================#

server {
    listen      %ip%:%proxy_ssl_port% ssl http2;
    server_name %domain_idn% %alias_idn%;
    index       index.php index.html index.htm;
    ssl_certificate      %ssl_pem%;
    ssl_certificate_key  %ssl_key%;
    ssl_stapling on;
    ssl_stapling_verify on;
    error_log  /var/log/%web_system%/domains/%domain%.error.log error;

    include %home%/%user%/conf/web/%domain%/nginx.hsts.conf*;

    location / {
        proxy_pass      https://%ip%:8083;
    }

This file has been truncated. show original

and

github.com

jaapmarcus/web-templates/blob/master/templates/nginx/cp.tpl

#=======================================================================#
# Default Web Domain Template                                           #
# DO NOT MODIFY THIS FILE! CHANGES WILL BE LOST WHEN REBUILDING DOMAINS #
#=======================================================================#

server {
    listen      %ip%:%proxy_port%;
    server_name %domain_idn% %alias_idn%;
    index       index.php index.html index.htm;
        
    include %home%/%user%/conf/web/%domain%/nginx.forcessl.conf*;

    location / {
    return 301 https://%domain_idn%/;
    }

    location /error/ {
        alias   %home%/%user%/web/%domain%/document_errors/;
    }

This file has been truncated. show original

And just block port 8083 / 2083

spectre · April 18, 2023, 7:32am

why would you open a perfect domain name with a port?? ie. your abc.com instead abc.com:2083

is there a reason you want to add a port number after the homepage?

reminding you, hestiacp needs port number not domain names

eris · April 18, 2023, 7:53am

Because Hestia runs under a separate process and it can’t share the port number with Nginx

The user complains that both: demo.hestiacp.com:8083 and hestiacp.xyz:8083 show the login page…

glonin.kz · April 18, 2023, 4:43pm

with this option, a single entry point to phpmyadmin will no longer work for you. I wonder when it will be fixed ?