Point Hestia Control Panel to Subdomain - Possible?

Jared · August 12, 2024, 5:58am

I’m using hestia with a domain name pointing to the server, and am able to log in fine at port 8083. However cloudflare seems to have issues forwarding traffic to that port, and I’d prefer to keep CF on for other parts of the domain.

I know I can just change the port to something like 80 or 8080, but those ports are more commonly attacked, so I hate to have those open on the main domain.

Is it possible to create a subdomain and have that be the hestia login page? for example: hestia.domain.com or even hestia.domain.com:8080 so as to be a less obvious hacking target?

eris · August 12, 2024, 6:03am

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

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

OR

github.com

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

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

server {
    listen      %ip%:%web_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

github.com

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

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

server {
    listen      %ip%:%web_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

Depending on your setup

Jared · August 12, 2024, 6:14am

Maybe I’m misunderstanding you, but aren’t those the templates for the user account domains?

My server has a dozen domains on user accounts already that I don’t want to change at all.

I just want my admin domain I’m using for the hestia server itself, not a user domain, to be able to login on a subdomain. The user accounts I want all left alone.

eris · August 12, 2024, 6:18am

Yes you need put in /usr/local/hestia/data/templates/web/nginx/ or /usr/local/hestia/data/templates/web/nginx/php-fpm folder and select the template for hostname.domain.com…

You can’t run “hestia” services just under port 80 as it will conflict with nginx service …

linkp · August 12, 2024, 3:54pm

You can also just use v-change-sys-port 2083 to configure access on port 2083 which Cloudflare does proxy.

system · September 11, 2024, 3:55pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.