Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
I think you are right and it may be the IDN portion and perhaps WordPress.COM dislikes processing http://kłusaki.pl.
I’ve no idea why. 😉
If you are up to it and as an experiment, can you substitute your WordPress Address (URL) and Site Address (URL) from
http://kłusaki.pl
to read
http://xn--kusaki-3db.pl
This is the ASCII version that I retrieved via http://www.dns.pl/cgi-bin/en_idntranslator.pl
You can do this on a temporary basis for testing by making a backup copy of your wp-config.php file (call it wp-config-SAVE.php`) and in the original file add these two lines.
define('WP_HOME','http://xn--kusaki-3db.pl');
define('WP_SITEURL','http://xn--kusaki-3db.pl');
That way if anything goes wrong then all you have to do it restore the saved backup copy of wp-config.php.
Let us know if you are willing to try that and if that works.
thanks for the replay
as you suggested, the punycode version works just fine 🙂
it does not affect the site usage in any way
best regards,
Bartek
Jan Dembowski, thanks for the tip! You’re right: we currently don’t support the Unicode representation of IDNs. We should 🙂
We’ll working on supporting them. For now, though, ASCII is the way to go.
I’m having the same problem on a new .org site. I’ve run Jetpack with no problem on other subdomains of mine, on the same host. The only difference I can see is that the subdomain name contains a number:
http://keep2thecode.fether.net
Do I need to escape the 2 or something?
ADDED: Never mind, it resolved on its own. The subdomain apparently took longer than usual to register. 🙂
