Access to the control panel without specifying the port number

titodevera · January 21, 2021, 2:23pm

Hi everyone!

My control panel URL looks like: https://mypanel.com:8083
Can I configure Hestia to access without specifying the 8083 port? Maybe some kind of redirection from the 80 port to the 8083?

Thanks so much

eris · January 21, 2021, 2:32pm

Would suggest the to use the ssl enabled site:

gist.github.com

https://gist.github.com/jaapmarcus/25b513629139af4ff45915fa154675b9

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%;
    ssl_certificate      %ssl_pem%;
    ssl_certificate_key  %ssl_key%;

This file has been truncated. show original

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%;
        
    include %home%/%user%/conf/web/%domain%/nginx.forcessl.conf*;

This file has been truncated. show original

titodevera · January 22, 2021, 9:18am

Hi eris!

I have configured the new template to the Nginx proxy for the panel´s web subdomain but it take no effects, it seems that all is working the same as with the default template.

Thank you

eris · January 22, 2021, 9:37am

What happens when you run nginx -t ?

titodevera · January 22, 2021, 10:04am

nginx: [emerg] open() “/etc/nginx/conf.d/domains/Error:.conf” failed (2: No such file or directory) in /etc/nginx/nginx.conf:149
nginx: configuration file /etc/nginx/nginx.conf test failed

Raphael · January 22, 2021, 10:23am

Sounds like you fucked up something with your template . You’ll need to check on your own whats on line 149 in your nginx.conf. We cant debug the system for you without access.

titodevera · January 22, 2021, 11:10am

Well! There was some old configuration files in the “/etc/nginx/conf.d/domains/” folder that contains syntax errors, after delete this files and resetting the template all is working as expected.
Thanks so much!

Raphael · January 22, 2021, 11:19am

I suggest to validate the config creation with v-rebuild-user user, just to prevent any issues during upgrade .

system · February 21, 2021, 11:19am

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