• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Domain will not enable with message "Domain is Expired"

G

ghirschel

Guest
Of course I would not be writing here if the domain was actually expired. It appears that my registrar did not renew in time, the domain was renewed a day later after expiring. WhoIs is listing the domain as active until Sept 2008, yet when I enable the site I receive this message:
"Domain is still disabled. The reason: Domain is Expired"
What/where is Plesk checking?

Thanks!
 
You must log in or register to reply here.

Similar threads

nethubonline
Forwarded to devs plesk repair mail fails with "Unable to find row with id 0 in dns_zone table" when DKIM is enabled and no DNS server is installed
Replies
1
Views
909
Sebahat.hadzhi
Sebahat.hadzhi
kristobal1969
Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails
Replies
12
Views
7K
NataliaA
N
N
Issue Enabling DNSSec for existing keys -- Workaround for double plesk bug.
Replies
2
Views
441
GCM
G
brother4
Issue plesk repair fs fails with custom DKIM selector: expected file but found symlink
Replies
3
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
D
Issue Outgoing mail limit increase in UI didn't take effect — turned out to be a service plan sync bug (18.0.80)
Replies
3
Views
7K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top