• Now I know there are quite a few people out there who have had similar issues with the 404 error from Jetpack – and ive read through almost all of them, but none of them seem to resolve my issue.

    I had a deeper look into it, and had a chat with my host (hostgator) and they said that it might because the line with the location might be missing from my wp-config.

    Could anyone with a bit more experience give me a hand here and tell me if thats the case/and how I can best fix this issue?

    My site: http://digitalcosmonaut.com

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi, I’m having the exact same problem. My host has offered me two options:

    1)Disable mod_security for my hosting account.
    2)Change my server to a new location.

    I’ve read on this link that mod_security is used for preventing hacking attacks like sql injection:

    http://onlamp.com/pub/a/apache/2003/11/26/mod_security.html

    So, am looking for a way to perhaps, selectively disable some aspects of mod_security, if that’s possible. Don’t want to change servers just now.

    A lot of people are getting the same error, so I will post whatever solution I get on here. Any help would be appreciated.

    Update: I’ve got mod_security disabled for now, and Jetpack has connected(!) I’m concerned about the solution though. Completely disabling mod_security doesn’t seem like a smart thing to do; my hosting provider’s saying it leaves my sites vulnerable to sql injection, among other things.

    I’m still looking for a smarter way to solve this problem. Backing up my hosted websites, just to be safe. I’ll try to reach the plugin authors, the mod_security author and WordPress. Maybe they can fix this nagging problem in WordPress’ next update.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Jetpack site_inaccessible [HTTP 404]’ is closed to new replies.