• 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.

Issue Plesk refused to connect

Bogdan1

Regular Pleskian
Hi,

I've just installed Plesk Onyx on Clean VPS(Centos 7)
Installation has been successfully installed. But when I try to connect to admin panel I'm getting "Plesk refused to connect". I tried repair plesk but everything is ok. Apache is running

[root@vps*** ~]# service httpd status

Redirecting to /bin/systemctl status httpd.service

httpd.service - The Apache HTTP Server

Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)

Active: active (running) since Sat 2018-03-03 01:02:23 CET; 15s ago

Docs: man:httpd(8)

man:apachectl(8)

Process: 20976 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)

Main PID: 20981 (httpd)

Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec"

Memory: 11.9M

CGroup: /system.slice/httpd.service

├─20981 /usr/sbin/httpd -DFOREGROUND

├─20983 /usr/sbin/httpd -DFOREGROUND

├─20984 /usr/sbin/httpd -DFOREGROUND

├─20985 /usr/sbin/httpd -DFOREGROUND

├─20986 /usr/sbin/httpd -DFOREGROUND

└─20987 /usr/sbin/httpd -DFOREGROUND


Mar 03 01:02:22 vps***.ovh.net systemd[1]: Starting The Apache HTTP Server...

Mar 03 01:02:23 vps***.ovh.net systemd[1]: Started The Apache HTTP Server.

2018/03/03 00:59:58 [notice] 17818#0: signal process started

[03-Mar-2018 00:56:47] NOTICE: fpm is running, pid 1932

[03-Mar-2018 00:56:47] NOTICE: ready to handle connections

[03-Mar-2018 00:56:47] NOTICE: systemd monitor interval set to 10000ms

[03-Mar-2018 01:00:01] NOTICE: Terminating ...

[03-Mar-2018 01:00:01] NOTICE: exiting, bye-bye!

[03-Mar-2018 01:00:01] NOTICE: fpm is running, pid 18000

[03-Mar-2018 01:00:01] NOTICE: ready to handle connections

[03-Mar-2018 01:00:01] NOTICE: systemd monitor interval set to 10000ms

2018/03/03 00:59:58 [notice] 17818#0: signal process started

empty

[2018-03-03 00:59:45] ERR [extension/letsencrypt] Domain validation failed for vps***$

Details:

Type: urn:acme:error:connection

Status: 400

Detail: Fetching http://vps***.ovh.net/.well-known/acme-challenge/quPrOlKas0wLyflWIN$

[2018-03-03 00:59:45] ERR [extension/letsencrypt] Domain validation failed: Invalid res$

Details:

Type: urn:acme:error:connection

Status: 400

Detail: Fetching http://vps***.ovh.net/.well-known/acme-challenge/quPrOlKas0wLyflWIN$

[2018-03-03 00:59:45] ERR [extension/letsencrypt] Failed to secure panel: Invalid respo$

Details:

Type: urn:acme:error:connection

Status: 400

Detail: Fetching http://vps***.ovh.net/.well-known/acme-challenge/quPrOlKas0wLyflWIN$




PS: I've also tried 17.8 preview and it works. So I don't understand why stable version refuse to work.
PS2: Is 17.8 preview stable enough to run a website on it?
 
Last edited:
17.8 is pretty stable as it is. I believe it should be released this month but don't quote me on that.

Have you tried both Plesk ports? 8443 for https, 8880 for http.

Run both the following to confirm; will show that there is something running on that port;

[root@plesk ~]# lsof -i:8443

[root@plesk ~]# lsof -i:8880


OVH typically preinstalls - Can you confirm you installed Plesk manually versus using an OVH template?
 
Yes I tried 8880 but getting the same error.
Yes I installed clean centos 7 and run plesk once-click installer.
Code:
sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)


COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

sw-cp-ser 21169 root 7u IPv4 116936 0t0 TCP *:pcsync-https (LISTEN)

sw-cp-ser 21169 root 9u IPv6 116938 0t0 TCP *:pcsync-https (LISTEN)

sw-cp-ser 21170 sw-cp-server 7u IPv4 116936 0t0 TCP *:pcsync-https (LISTEN)

sw-cp-ser 21170 sw-cp-server 9u IPv6 116938 0t0 TCP *:pcsync-https (LISTEN)


COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

sw-cp-ser 21169 root 8u IPv4 116937 0t0 TCP *:cddbp-alt (LISTEN)

sw-cp-ser 21169 root 10u IPv6 116939 0t0 TCP *:cddbp-alt (LISTEN)

sw-cp-ser 21170 sw-cp-server 8u IPv4 116937 0t0 TCP *:cddbp-alt (LISTEN)

sw-cp-ser 21170 sw-cp-server 10u IPv6 116939 0t0 TCP *:cddbp-alt (LISTEN)
 
Try to telnet to it from your local machine;

Code:
Marks-MacBook-Pro:~ MarkyMark$ telnet plesk.wired-solutions.net 8443
Trying 107.189.48.141...
Connected to plesk.wired-solutions.net.
Escape character is '^]'.
 
Code:
Macintosh:~ bogdandovgopol$ telnet 54.**.**.*** 8443
Trying 54.**.**.*** ...
telnet: connect to address 54.**.**.***: Connection refused
telnet: Unable to connect to remote host
 
Last edited:
Check the OVH Firewall, that has to be it.

You do get bonus points for using a Mac :D
 
Check the OVH Firewall, that has to be it.

You do get bonus points for using a Mac :D

Looks like there is nothing in OVH's firewall. I can only create.
As I said for some reason plesk preview working just fine except it's always(every click) logging out .

Yezu69A.png


Thanks for the bonus points :D
 
Last edited:
Damn, which repair options have you tried? plesk repair installation?
 
This one:

  • plesk repair all -y - Checks the Plesk installation and all Plesk services. The utility will run in the repair mode (the utility attempts to resolve any issues it detects).
 
Alright, one more attempt, try flushing iptables;

[root@plesk ~]# iptables -F
 
Back
Top