• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Problem Installing

nolyoly

New Pleskian
So, I'm running CentOS 6 on a VPS. I just ran the installer in the command line. It then told me to access myurl.com:8443 etc.

When I attempt to access that URL I'm getting a server not found error. I'm guessing this has something to do with my iptables? If anyone can help me get this runnning I'd greatly appreciate it.

Here's a copy of what comes up when I VIM my iptables too.

Code:
[root@saint ~]# vi /etc/sysconfig/iptables            

# Generated by iptables-save v1.4.7 on Mon Jul 17 20:33:43 2017
*security
:INPUT ACCEPT [66:4572]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [45:4852]
COMMIT
# Completed on Mon Jul 17 20:33:43 2017
# Generated by iptables-save v1.4.7 on Mon Jul 17 20:33:43 2017
*mangle
:PREROUTING ACCEPT [73:4934]
:INPUT ACCEPT [66:4572]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [45:4852]
:POSTROUTING ACCEPT [45:4852]
COMMIT
# Completed on Mon Jul 17 20:33:43 2017
# Generated by iptables-save v1.4.7 on Mon Jul 17 20:33:43 2017
*filter
:INPUT ACCEPT [66:4572]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [45:4852]
COMMIT
# Completed on Mon Jul 17 20:33:43 2017

I have no idea what I did wrong. I've installed Plesk perfectly fine in the past. This was done on a fresh install of CentOS 6 on my VPS as well.
 
Last edited:
Please be sure that hostname myurl.com is resolvable. Try to use IP address of server instead of hostname.
 
Back
Top