• 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 Name Not Resolved Issues

K

KooTjoo

Basic Pleskian
Hi,

I am using Plesk v12.5.30_build1205150826.19 os_CentOS 7

I have strange issues with only 1 subdomain. I have created subdomain like I always do and it is working Ok for a while. After some time it stops working and can't find the page (ERR_NAME_NOT_RESOLVED). If I wait few minutes or restart server it comes up again. The issue happens only with 1 subdomain all other (sub)domains work wel.

Is there a way to find out what is casing this.

KooTjoo
 
You must log in or register to reply here.

Similar threads

D
Issue Plesk stops responding
Replies
1
Views
1K
scsa20
scsa20
Azurel
Issue MariaDB 11.8.8: STRICT_TRANS_TABLES suddenly enabled after reboot AlmaLinux 9.7 → 9.8
Replies
2
Views
588
Azurel
Azurel
N
Issue Issues with migration from web host to web admin
Replies
2
Views
4K
nelteren
N
B
Issue Plesk task manager service trying to run task with id that does not exist
Replies
2
Views
3K
BigBlock
B
Polli
Nameserver DNS entrys for subdomains are set wrong when plesk is primary DNS
Replies
2
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top