Jetpack by WordPress.com
[resolved] Jetpack couldn't resolve IDN domain (5 posts)

  1. klusaki
    Posted 4 years ago #


    I want to use latest jetpack on my wp powered blog - http://kłusaki.pl
    The problem is its IDN domain and I've got error trying to connect to WordPress.com:

    Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed Couldn't resolve host 'kłusaki.pl']

    is there some workaround to that problem?

    best regards,


  2. 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


    to read


    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.


    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.

  3. klusaki
    Posted 4 years ago #

    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,

  4. Michael Adams (mdawaffe)
    Plugin Author

    Posted 4 years ago #

    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.

  5. Keep2theCode
    Posted 4 years ago #

    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:

    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. :-)

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Jetpack by WordPress.com
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic