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

Subdomain on dedicated IP - issue

E

EricVis

Basic Pleskian
I have a domain1.com set up on IP1
I have subdomain set up separately as domain ssl.domain1.com on IP2 (dedicated IP)

1) It all worked until yesterday but today when I ping ssl.domain1.com it returns IP1 instead of IP2

2) When I access https://ssl.domain1.com I get 404, when I access http://ssl.domain1.com I get correct webiste (subdomain)

What is going on? I haven't changed anything, autoupdates disabled
Plesk 11.0.9 Update #61
 
You must log in or register to reply here.

Similar threads

EnriqueR
Question Incoming mail is stored in Junk folder
Replies
6
Views
6K
EnriqueR
EnriqueR
M
Resolved Lets Encrypt not issuing certs for subdomains
Replies
2
Views
4K
mendip_discovery
M
H
Question SSH user can see other subdomain directories even with chrooted shell?
Replies
3
Views
4K
Raul A.
R
Talistech
Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP
Replies
8
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
C
Question Strange SNI (?) issue related to IPv6 (?)
Replies
2
Views
5K
Carbon Dioxide
C
Back
Top