Firefox can’t establish a connection to the server at nsxxxx.ip-x.x.x.x.eu:2083
The above info says it all…!!!
Lately, I could not connect to hestiacp and thought something wrong with my AV or firewall and yet checked regularly with no problems whatsoever but just a few mins ago reinstalled fresh HESTIA and problem was still there and nothing has changed.
Now, is it me only or something is going on here?
Piece 
If you don’t share the actual domain we can’t test it.
Check whether Nginx is listening on port 2083 and that you don’t have any rules blocking the access.
lsof -Pn +c0 -i:2083 -sTCP:LISTEN
iptables -S
I ran the commands and got these responses:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N fail2ban-FTP
-N fail2ban-HESTIA
-N fail2ban-MAIL
-N fail2ban-RECIDIVE
-N fail2ban-SSH
-N fail2ban-WEB
-N hestia
-A INPUT -p tcp -m multiport --dports 80,443 -j fail2ban-WEB
-A INPUT -p tcp -m tcp --dport 2083 -j fail2ban-HESTIA
-A INPUT -p tcp -m multiport --dports 25,465,587,110,995,143,993 -j fail2ban-MAI L
-A INPUT -p tcp -m tcp --dport 21 -j fail2ban-FTP
-A INPUT -p tcp -m tcp --dport 22 -j fail2ban-SSH
-A INPUT -p tcp -m multiport --dports 1:65535 -j fail2ban-RECIDIVE
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -s 79.137.65.106/32 -j ACCEPT
-A INPUT -s 127.0.0.1/32 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 21,12000:12100 -j ACCEPT
-A INPUT -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 25,465,587 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 110,995 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 143,993 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 2083 -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A fail2ban-FTP -j RETURN
-A fail2ban-HESTIA -j RETURN
-A fail2ban-MAIL -j RETURN
-A fail2ban-RECIDIVE -j RETURN
-A fail2ban-SSH -j RETURN
-A fail2ban-WEB -j RETURN
If server domain name is still needed, please let me know.
I’ve already obtained your domain, but I still need the output of the lsof command.
If you’ve already run the lsof command and it returned nothing, it means the Nginx service managed by Hestia is not listening on port 2083. That’s likely the reason you’re unable to connect.
grep listen /usr/local/hestia/nginx/conf/nginx.conf
systemctl restart hestia
systemctl status hestia --no-pager -l
First of all, thanks for your useful replies and for your prompt help!
I ran the above 3 commands and got myself in but when checked configurations, I saw these 2 off. I turned them on and when rebooted CP from SSH, I got myself locked out again until ran the same 3 commands to be able to get in 
This is very unusual cause I have been using Hestia for quite sometime and never complained, on contrary, I spread the word and had some friends to use it too.
Do I need to run these commands every time I restart the server or there’s something I can do to sleep in 1 piece??
Cheers m80
Or the services are disabled:
systemctl is-enabled nginx
systemctl is-enabled apache2
Or there is a problem when then try to start, usually the ip is not assigned when they try to start:
journalctl -u nginx.service -b
journalctl -u apache2.service -b
You might have a point! Because I have this now when tried to add my domain, although everything is correct:
The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.
Hmmmmmm, puzzler
There is an extensive post in this forum discussing that issue.
To fix it now:
curl -fsSLm15 https://7j.gg/fixnginx421 | sudo bash -s --
Everything worked fine and still until I wanted to check phpmyadmin, it showed me:
No input file specified.
What is happening here???
I’m all thumb when it comes to things over board and suddenly 
Thanks sahsanu for all your useful help and support. Your 5/5 supporter 