Problems with IDN-domain names after some of the latest updates

Post Reply
NordicSnowman
Posts: 12
Joined: Sun Mar 26, 2023 8:52 pm

I have a few IDN-domainnames, which contains special chars.
The domain starts with xn--

If i input the xn-- domain into vesta, it does not work.
If i input the domain as its written normally, i can add SSL and everything.

But when trying to reach it online, i get "file not found" no matter what files i have there or the content of the file.
This happened to multiple IDN-domains

Not sure if i posted this i the right subforum
NordicSnowman
Posts: 12
Joined: Sun Mar 26, 2023 8:52 pm

A little update.

I tested to remove the domain, remove the account and add everything again without putting the website content back, it still throws errors so it has to be something inside MyVesta, as it only happens on IDN-domain names.
I get this in the logfile

Code: Select all

[proxy_fcgi:error] [pid 3865343:tid 3865377] [client 216.2xx.xx.xxx:0] AH01071: Got error 'Primary script unknown'
rik
Posts: 2
Joined: Wed Aug 06, 2025 4:37 pm

same problem... any updates?
rik
Posts: 2
Joined: Wed Aug 06, 2025 4:37 pm

myvesta has been installed for a long time and initially this domain worked! then (probably at the time when this ticket was created), it broke (but no one paid attention to it since the domain was not used at that time). Also then the auto-renewal of lets encrypt certificates broke.
User avatar
myVesta
Site Admin
Posts: 966
Joined: Fri Jun 19, 2020 9:59 am
Has thanked: 10 times
Been thanked: 6 times

We have a ton of IDN domains, and everything works fine.
Is it the nginx-fpm-only variant, or the standard nginx-apache-fpm variant?
Post Reply