• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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