• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved No more access to Plesk dashboard: firewall issue?

Jean-Luc GARNIER

Basic Pleskian
Dear Community,

I've updated the Plesk configuration on my VPS on last Friday and accepted to install the firewall, but didn't activate it.

This morning, my mail client complained about not being able to access the server, other tools (in subdomains) seem to be locked and I don't have any access to the dashboard to check the Plesk config and fix this. Ssh, http, https, dns, smtp services are all invalid, so I'm stuck...

I'm wondering whether I could access to some config file to check/fix this config, as my hosting provider provide a "rescue OS function" to restart my server with a basic Ubuntu OS and a SSH access.

Thanks in advance for any help!
 
You can test port access with:

telnet 127..0.0.1 80

or maybe with:

nc -zv 127.0.0.1 80

If your problem is your firewall and if you have access through SSH you can review your iptables configuration:

iptables -L
 
Thanks Cristian for the tip! By the way, the server is now up and running again, so I strongly suspect the issue was on the hosting side! And no info message of course :mad:!
 
Back
Top