After DNS Update, Hestia Panel Not Accessible

Draybaba · March 4, 2024, 9:05am

Hello everyone,

I have been using Hestia panel for some time and it’s working fine but then I realized the SSL is not active on the www version of my domain name, essentially, I can’t access the www version of my website. It was showing the “too many redirects error message”. I was using Cloudflare to manage my DNS at this time.

My domain registrar tried to help but couldn’t.

So, I decided to delete my DNS settings from Cloudflare and manage the DNS directly on my domain registrar.

Ever since I did this, I couldn’t access my Hestia panel anymore.

I have changed the port on my Oracle Cloud instance from 2083 (for Cloudflare), to 8083.

The worst part is, I can’t access my instance too.

Any idea of what could have gone wrong please?

Note: my website is working perfectly with active SSL i.e. its www and non-www versions. Just that, I can’t access my Hestia panel.

Draybaba · March 4, 2024, 11:07am

SOLVED
I was able to resolve the issue by reconnecting the website back to Cloudflare and managing the DNS through Cloudflare again.

After a few hours and the NS (nameserver) got propagated, I visited https://hcp.mydomain.com:2083 and I was able to see my Hestia panel login screen again

After successful login as the admin, I clicked on the server cog icon > firewall.

Then added a new firewall rule to allow port 8083

Next, I log in as my website user (not admin this time), edited the web domain and went straight to the SSL section and then added the www version of my website in the “Aliases” field section

Now, when I checked the www and non-www versions of my website, i.e. mydomain.com and www.mydomain.com they’re both working perfectly!

NOTE: I added the firewall rule of 8083 to test if I will be able to still access my Hestia panel if I disconnect Cloudflare and instead manage the DNS directly from my domain registrar. As of this writing, the DNS with Cloudflare hasn’t propagated 100%, so I will need to wait, disconnect again, wait again for it to propagate with my domain registrar. If it works, I will come update this answer.

Also, I added and allow the 8083 port so the www version of my website could work with my domain registrar since that port is necessary, to be able to access Hestia panel without Cloudflare and it’s open in my Oracle Cloud instance ingress rules, hence, the port needs to be open too in my Hestia panel firewall rule for the www versions too to work even after connecting to Cloudflare.

Hope it helps someone.
Damilare.

mih · March 4, 2024, 7:51pm

github.com

hestiacp/hestiacp/blob/release/bin/v-add-letsencrypt-host

#!/bin/bash
# info: add letsencrypt for host and backend
# options: NONE
#
# example: v-add-letsencrypt-host
#
# This function check and validates the backend certificate and generate
# a new let's encrypt certificate.

#----------------------------------------------------------#
#                Variables & Functions                     #
#----------------------------------------------------------#

# Includes
# shellcheck source=/etc/hestiacp/hestia.conf
source /etc/hestiacp/hestia.conf
# shellcheck source=/usr/local/hestia/func/main.sh
source $HESTIA/func/main.sh
# shellcheck source=/usr/local/hestia/func/domain.sh
source $HESTIA/func/domain.sh

This file has been truncated. show original

v-add-letsencrypt-host

system · April 3, 2024, 7:52pm

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