• 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 IDN Domain Routing (Resolving Domainname) Problem

GeeBee

New Pleskian
IDN Domains are not resolved, causing a 403 error in Browser

Forbidden
You don't have permission to access / on this server.


OS:
Plesk Onyx Version 17.5.3 Update #6
Ubuntu 16.04.2 LTS‬

Domain was set with IDN coding but this should not be issue since other similar server running on Plesk 12.5 and Ubuntu 14 dont have this problem.
 
Have you tried to fix it with

# plesk repair fs
# plesk repair web

?
 
My assumption was wrong. The problem was not connected to Plesk.

I transferred the domain and changed the IP address pointing to the server running with Plesk. I was used to have a stable routing after minutes. But with the IDN domain it took two full days. After that time the problem vanished. So nothing to do with Plesk, more with the fact that nameserverrouting ist not fully stable in the process of domain transfer and takes ages for IDN domains.
 
Back
Top