Page 1 of 1
Problems with IDN-domain names after some of the latest updates
Posted: Fri Oct 04, 2024 4:12 pm
by NordicSnowman
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
Re: Problems with IDN-domain names after some of the latest updates
Posted: Fri Oct 04, 2024 8:10 pm
by NordicSnowman
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'
Re: Problems with IDN-domain names after some of the latest updates
Posted: Wed Aug 06, 2025 4:38 pm
by rik
same problem... any updates?
Re: Problems with IDN-domain names after some of the latest updates
Posted: Thu Aug 07, 2025 7:39 am
by rik
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.
Re: Problems with IDN-domain names after some of the latest updates
Posted: Thu Aug 07, 2025 10:39 am
by myVesta
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?
Re: Problems with IDN-domain names after some of the latest updates
Posted: Wed Oct 29, 2025 9:57 am
by NordicSnowman
myVesta wrote: ↑Thu Aug 07, 2025 10:39 am
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?
I have tried everything, all variants and settings.
If i add a domain, its added but does not work.
I have 7 myvesta-servers and it doesnt work on any of them.
The domain is added in vesta
DNS added
Website doesn not work, just shows file not found.
And when trying to remove the domain - its stuck, it says the domain doesnt exist, i cannot remove the account either.
But when i killed the row in the dns-server, and then removed the web-domina in vesta, the server crashed totally - websites worked but MyVesta was beyond saving, i had to re-install on top of the old one to wake it up again and import all user accounts.
Any suggestions what i can try? i have set up a MyVestaCP machine at home now on a server i can test stuff on.