• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved I can't access my plesk

Solarom

New Pleskian
Server operating system version
Ubuntu 22.04 LTS (Jammy Jellyfish)
Plesk version and microupdate number
Plesk Obsidian 18.0.59.2
Hello, I can no longer access my administration page.
When I try to access port 8443, the page displays: ‘ERR_CONNECTION_TIMED_OUT’.

All websites are accessible. Only the administration page is no longer accessible.
I try to access it from web-plesk.araik.fr
I no longer own the araik.fr domain name
Could this be the problem?

If so, how can I change it if I can no longer access the panel?
 
Hi @Solarom

It is worth confirming that your server is listening on Port 8443. I'm also on a Ubuntu 22.04 based server and get the following when checking which ports are open:
Code:
alex@mypleskserver:~$ sudo ss -tl | grep 8443
LISTEN 0      511                           0.0.0.0:8443             0.0.0.0:*
LISTEN 0      511                              [::]:8443                [::]:*
alex@mypleskserver:~$

Note that this is showing both IPv4 and IPv6 listening sockets - you may only get one of the two that I get. If your server shows something similar then I think that something is firewalling port 8443 and stopping you getting to it. This could either be on your server or in your ISP's network. The reason that I say this is that connections are timing out (being dropped). If they were reaching the server and the port wasn't open, it would fail immediately.
Code:
alex@myhomeserver:/tmp$ wget https://195.110.35.159:8443/
--2024-04-24 23:58:03--  https://195.110.35.159:8443/
Connecting to 195.110.35.159:8443... failed: Connection timed out.
Retrying.

--2024-04-25 00:00:14--  (try: 2)  https://195.110.35.159:8443/
Connecting to 195.110.35.159:8443... failed: Connection timed out.
Retrying.

--2024-04-25 00:02:26--  (try: 3)  https://195.110.35.159:8443/
Connecting to 195.110.35.159:8443... failed: Connection timed out.
Retrying.

--2024-04-25 00:04:40--  (try: 4)  https://195.110.35.159:8443/
Connecting to 195.110.35.159:8443... ^C
alex@myhomeserver:/tmp$

I hope that this helps you get to the bottom of the issue.
 
No, I can't access your IP your port 8443 either. I addition to the great suggestion of @Alex Presland, it might be worth to check if the Plesk service component is actually running. You can use following commands to check the status:

Code:
service sw-engine status
service sw-cp-server status
 
Okay, I have carried out the orders you requested.
What do we do now please?
 

Attachments

  • Num1.PNG
    Num1.PNG
    24.8 KB · Views: 8
  • Num2.PNG
    Num2.PNG
    35.8 KB · Views: 8
  • Num3.PNG
    Num3.PNG
    4.2 KB · Views: 7
The Plesk service components are running and port 8443 looks to be open on your server. Yet something is blocking access to port 8443. It's hard to say what that is exactly. My best guess would be the firewall of your hosting provider. I would suggest to contact them and explain that access to port 8443 is blocked, but open on your server.

Alternatively you can configure a custom URL to access Plesk without port 8443. To configure a custom URL you can use the following command: plesk bin admin --enable-access-domain plesk.example.com (Replace plesk.example.com with your own URL.)

More information on customizing the Plesk URL can be found here:
 
Last edited:
but I can't access it even using my phone. It's not the same operator though.
Sorry, wrong wording... please contact your SERVER PROVIDER and ask them to open up inbound port 8443 to your server in their firewall.

@Kaspar has also given a good alternate solution of using the "enable access domain" feature, if your server provider won't open up inbound port 8443.
 
Back
Top