Routing Problems from Webserver to jetpack.wordpress.com

  • Unknown's avatar
    netzkulturde · Member ·

    Dear community,

    at first sorry for my bad English.

    I have a the problem, that my WordPress can´t connect with jetpack.

    I get the Error Message:
    „Jetpack konnte WordPress.com nicht kontaktieren: Register_http_request_failed. ….“
    „… connect () timed out!“

    My website with WordPress is “www.infra-struktur.de”

    This isn´t the typical problem with Http / HTTPS.

    The problem is, that I can´t connect to jetpack.wordpress.com or wordpress.com.

    I tried the following tasks:
    – ping jetpack.wordpress.com -> no response
    – ping 192.0.78.26 -> no response
    – Traceroute jetpack.wordpress.com -> not successful
    – Traceroute 192.0.78.26 – > not successful

    The following command „tracepath jetpack.wordpress.com“ shows me:
    1: astra2474 (myIP) 0.074ms pmtu 1500
    1: static-ip.inaddr.ip-pool.com (IPHoster) 1.406ms
    1: static-ip.inaddr.ip-pool.com (IP-Hoster) 1.226ms
    2: static-ip-217-118-23-1.inaddr.ip-pool.com (217.118.23.1) 0.404ms
    3: 217.118.16.29 (217.118.16.29) 0.774ms asymm 2
    4: 217.118.16.129 (217.118.16.129) 11.140ms
    5: 217.118.16.129 (217.118.16.129) 3.575ms asymm 4
    6: 80.237.129.37 (80.237.129.37) 3.470ms
    7: no reply
    8: no reply
    9: no reply
    …
    …
    31: no reply
    Too many hops: pmtu 1500
    Resume: pmtu 1500

    I spoke with the support department from my webhoster who hosts this page. He told me, that they don´t block any outgoing transport.
    He told me, that the HOB 7 is the wordpress server.

    Is it Possible that wordpress blocks my IP Address or my IP address range?

    I also spoke to the jetpack support, but they couldn´t really help me.
    They said that the problem could be that the XML-RPC is currently blocked.

    When trying http://www.infra-struktur.de/xmlrpc.php I get a 403 Forbidden message.

    Does it mean that the option is disabled in wp-admin or does anything else blocks it?
    How can I unblock it?

    In the Internet it says that this option is enabled by default.
    In WordPress 3.5 I could check a checkbox called XML-RPC under menu Write.
    Under WordPress 4.2.2 this Option isn’t there. Additionally, I changed the rights and the owner under linux with chmod and chown. It doesn’t resolve the error 403.

    I hope someone can help me with that.

    Cheers
    Marcel

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    rachelmcr · Member ·

    Hi Marcel,

    When trying http://www.infra-struktur.de/xmlrpc.php I get a 403 Forbidden message.

    That is the problem. Until that is resolved, Jetpack won’t be able to connect with your site.

    Can you please ask your website host why that link returns a 403 error? That may be due to a block installed by your website host, or a rule in your site’s .htaccess file.

    You will need to resolve that error with your website host. If you have any further trouble with Jetpack after that, please let me know.

  • Unknown's avatar
    netzkulturde · Member ·

    Hi rachelmcr,

    I have fixed the error with the inaccessible xmlrp.php. Just as you said, it was a blocking rule in the htaccess File.

    But the problem stays the same. I get the same Error as before.

    FYI:
    I added the Line “define( ‘JETPACK_CLIENT__HTTPS’, ‘NEVER’ );” into the wp-config.php.
    It has also not changed anything.

    Any other suggestions. Do you need more information’s?

  • Unknown's avatar
    rachelmcr · Member ·

    Hi Marcel,

    Can you please delete and reinstall the Jetpack plugin, and then try again to connect it to WordPress.com?

    If that still doesn’t work, please use Jetpack’s Debugger module to send us some more information about your site. To do so, follow these steps:

    1. Go to the Jetpack page in your dashboard.
    2. Click on the “Debug” link in the footer of the page.
    3. Click the link that says “click here to contact Jetpack support.”
    4. Fill in the description box and your name and email address.
    5. Click the “Contact Support” button.

    Thanks!

  • Unknown's avatar
    netzkulturde · Member ·

    Hi Rachelmcr,

    re installing the plugin doesn´t helped and I can´t try the second suggestion.

    If I hit the button “Debug-Infos”, (this was the only debug button) I get this error:

    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Web Server at infra-struktur.de

  • Unknown's avatar
    rachelmcr · Member ·

    Hi Marcel,

    Can you please contact your website host for more details about that Internal Server Error? That indicates a problem with your server that might point to the overall problem you’re having with Jetpack.

    If your host isn’t able to resolve that error, it would help to know more about your server setup and any errors indicated in the server error log. You’re welcome to send those details privately if you prefer using the Jetpack Support contact form.

  • Unknown's avatar
    netzkulturde · Member ·

    Hi rachelmcr,

    I think and this seems legit, that when clicking the button “Debug” my WordPress tries to connect to jetpack.wordpress.com.

    If I ping jetpack.wordpress.com, I get no response.
    If I ping jetpack.wordpress.com, from my own pc in another Network I get an answer.
    Thats why I think that there is a routing problem.

    After testing the problem seems to be, that the connection gets lost at the last server direct before connecting to the WordPress servers. That is what the administrator of my webhoster said.

    The error logs are all ok. There is nothing special in it.

  • kraftbj · Staff ·

    Howdy!

    I think you’ve found the issue. For the earlier internal service error, if the error logs aren’t reporting anything, then your hosting provider may need to increase the level of php error logging. There really should be something there!

    For the ping issue, could you ask your webhost for assistance to confirm that your server is unable to reach WordPress.com’s servers? Also, please let us know your server’s public IP for us to investigate on our end.

    Thanks!

  • Unknown's avatar
    netzkulturde · Member ·

    I contacted my webhoster 2 Weeks ago and he told me that WordPress blocks my external IP Address. He tried two traceroute-tests from different sources.
    First he tested a traceroute from our Server to the Domain wordpress.com, with the exact same error as described in post one.
    After that he tests it from his workstation. He told me that the route was exactly the same and that hob 7 is a server of WordPress. He could establish a connection from his workstation to WordPress.

    To get the IP only ping the http://www.infra-struktur.de. It’s the Real IP Address. I don´t want to post the IP in plaintext.

    Cheers
    Marcel

  • kraftbj · Staff ·

    Thanks Marcel.

    I’m checking with our systems team about the blocked IP. That said, I can’t recall a time when a blocked IP caused an internal server error when trying to connect.

    Your server’s PHP error log should contain details about the specific error you’re seeing as it might be related or totally unrelated to any IP block, if present.

    In short, we’re checking on the IP, but there really should be something in the error log to correspond with the time of the request if it resulted in an Internal Service Error.

    Cheers!

  • Unknown's avatar
    netzkulturde · Member ·

    Dear kraftbj,

    did you found the Problem?

    Now I am able to ping jetpack.wordpress.com. I also updated Jetpack to the last version released this morning and now it works.

    FyI I found the right log files:

    [Mon Jul 06 15:07:17 2015] [warn] [client 79.230.237.191] mod_fcgid: read data timeout in 45 seconds, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
[Mon Jul 06 15:07:17 2015] [error] [client 79.230.237.191] Premature end of script headers: admin.php, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
[Mon Jul 06 15:07:23 2015] [warn] [client 79.230.237.191] mod_fcgid: read data timeout in 45 seconds, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
[Mon Jul 06 15:07:23 2015] [error] [client 79.230.237.191] Premature end of script headers: admin.php, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
[Mon Jul 06 15:07:32 2015] [warn] [client 79.230.237.191] mod_fcgid: read data timeout in 45 seconds, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack
[Mon Jul 06 15:07:32 2015] [error] [client 79.230.237.191] Premature end of script headers: admin.php, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack
[Mon Jul 06 15:35:59 2015] [warn] [client 79.230.237.191] mod_fcgid: read data timeout in 45 seconds, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
[Mon Jul 06 15:35:59 2015] [error] [client 79.230.237.191] Premature end of script headers: admin.php, referer: http://www.infra-struktur.de/wp-admin/admin.php?page=jetpack&action=register&_wpnonce=e91db0bd88
  • The topic ‘Routing Problems from Webserver to jetpack.wordpress.com’ is closed to new replies.