Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter DJChupa13

    (@djchupa13)

    I really want to say thanks to both of you for helping me this much.

    I have identified the problem. It’s my host, as we expected.

    Under Plesk hosting, my PHP version is 5.4, and mySQL is 5.5.
    This does not meet the requirements for WordPress.

    Switching from Plesk hosting to cPanel should resolve my issue, so I’m considering doing that. GoDaddy is helping me out with the switch, refunding the Plesk Hosting and switching me over to a cPanel economy plan instead.

    I’ll write back once the switch takes place. Again, thanks!

    Thread Starter DJChupa13

    (@djchupa13)

    Yes, it’s definitely there. Even fetched another copy of Jetpack and re-uploaded just to make sure the file wasn’t damaged, but no changes.

    Thread Starter DJChupa13

    (@djchupa13)

    That’s correct, thanks Tim.

    I’ll be opening a support ticket with my host shortly. Maybe they can give me some insight. In the time being, are there any other suggestions?

    Thread Starter DJChupa13

    (@djchupa13)

    Hey Tim, I’m actually hosting this with GoDaddy (Plesk), so I’m not in a local hosting situation. I decided to give your solution a try anyways, but unfortunately, it did not change anything. Thanks anyways!

    Thread Starter DJChupa13

    (@djchupa13)

    Neat little trick. I actually errored out in a different way this time. Using the install method you described (Plugins > Add New > Search for Jetpack > hit install button), I instead was redirected back to the “Add Plugins” page with this error message inline:

    Installation failed: 500 Internal Server Error <!--[if lte IE 6]><![endif]--> 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 nathanabshire.com <!-- - Unfortunately, Microsoft has added a clever new - "feature" to Internet Explorer. If the text of - an error's message is "too small", specifically - less than 512 bytes, Internet Explorer returns - its own error message. You can turn that off, - but it's pretty tricky to find switch called - "smart error messages". That means, of course, - that short error messages are censored by default. - IIS always returns error messages that are long - enough to make Internet Explorer happy. The - workaround is pretty simple: pad the error - message with a big comment like this to push it - over the five hundred and twelve bytes minimum. - Of course, that's exactly what you're reading - right now. -->

    So…same error, different presentation (probably won’t matter much). Here’s the debug.log contents:

    [03-Nov-2016 22:29:33 UTC] PHP Warning:  require_once(G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php): failed to open stream: No such file or directory in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    [03-Nov-2016 22:29:33 UTC] PHP Fatal error:  require_once(): Failed opening required 'G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php' (include_path='.;.\includes;.\pear') in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    [03-Nov-2016 22:29:36 UTC] PHP Warning:  require_once(G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php): failed to open stream: No such file or directory in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    [03-Nov-2016 22:29:36 UTC] PHP Fatal error:  require_once(): Failed opening required 'G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php' (include_path='.;.\includes;.\pear') in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    [03-Nov-2016 22:29:36 UTC] PHP Warning:  require_once(G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php): failed to open stream: No such file or directory in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    [03-Nov-2016 22:29:36 UTC] PHP Fatal error:  require_once(): Failed opening required 'G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack/sync/class.jetpack-sync-actions.php' (include_path='.;.\includes;.\pear') in G:\PleskVhosts\nathanabshire.com\httpdocs\wp-content\plugins\jetpack\jetpack.php on line 51
    DJChupa13

    (@djchupa13)

    I’m having the same issue. However, I have no other plugins installed.

    When I activate the Jetpack plugin (latest version), I immediately get the Internal Server Error message. The message persists throughout all of WP-Admin, and through all of my site’s pages except for the home page (probably caching).

    Deleting the plugin folder (thus deactivating the plugin) resolves the issue immediately.

    I have deleted and manually re-added the Jetpack plugin folder multiple times, trying a couple of different scenarios with the PHP alloc numbers. Nothing has worked so far. I’m currently set to 128M alloc, with a max of 256M.

    This problem persists after a fresh manual install of WordPress. I’m using GoDaddy (Plesk) for hosting. Their error logs are way over my head, but if you’d like me to post today’s logs, I certainly can.

    This problem has persisted over several versions of Jetpack. By the way, I cannot install Jetpack using the auto-install tool. When I click the blue “install” button at the bottom of the page (after entering my site’s URL) it queues up the plugin install. However, when it attempts to communicate with my WP site, it idles out into the same 500 Internal Server Error page. The plugin folder is created and populated successfully (I can see it through FTP) so I’m guessing it errors out when attempting to activate the plugin, just as it would manually.

    I’ve been fighting this issue for nearly a year. SOS! Please send help!

    DJChupa13

    (@djchupa13)

    I’m having the same issue. However, increasing PHP memory allocation (as @jeherve suggested) did not resolve the problem.

    When I activate the Jetpack plugin (latest version), I immediately get the Internal Server Error message. The message persists throughout all of WP-Admin, and through all of my site’s pages except for the home page (probably caching).

    Deleting the plugin folder (thus deactivating the plugin) resolves the issue immediately.

    I have deleted and manually re-added the Jetpack plugin folder multiple times, trying a couple of different scenarios with the PHP alloc numbers. Nothing has worked so far. I’m currently set to 128M alloc, with a max of 256M.

    This problem persists after a fresh manual install of WordPress. I’m using GoDaddy (Plesk) for hosting. Their error logs are way over my head, but if you’d like me to post today’s logs, I certainly can.

    This problem has persisted over several versions of Jetpack. By the way, I cannot install Jetpack using the auto-install tool. When I click the blue “install” button at the bottom of the page (after entering my site’s URL) it queues up the plugin install. However, when it attempts to communicate with my WP site, it idles out into the same 500 Internal Server Error page. The plugin folder is created and populated successfully (I can see it through FTP) so I’m guessing it errors out when attempting to activate the plugin, just as it would manually.

    I’ve been fighting this issue for nearly a year. SOS! Please send help!

    Thread Starter DJChupa13

    (@djchupa13)

    It’s sent. Thanks again for the help!

    ~Nathan

    Thread Starter DJChupa13

    (@djchupa13)

    Ryan!

    Thanks very much for your help. I’ve reconnected JetPack to WordPress a few moments ago. Please do whatever you need to do.

    ~Nathan

    Thread Starter DJChupa13

    (@djchupa13)

    Bump. I’d be happy to clarify the problem if need be.

    Thread Starter DJChupa13

    (@djchupa13)

    Oh good, now it’s on desktops, too. Never saw it in Chrome, but I’m now seeing it in Firefox and IE.

    Thread Starter DJChupa13

    (@djchupa13)

    And now I get this via email:

    New user registration on your site Nathan Abshire:
    
    Username: RosemaryLemon
    
    E-mail: rosemarylemon [at] space.maildin [dot] com

    …and two others like it from the same domain, which I googled and it looks like straight up spam.

    At least in hesster’s case, try removing the jetpack plugin under your plugins directory. Or, better yet, try disconnecting then reconnecting Jetpack from WordPress.com.

    Thread Starter DJChupa13

    (@djchupa13)

    I’ve installed Sucuri Security which found modified core files (five total: two jquery libraries, two svg media elements, and a license.txt at /wpincludes/images/crystal). It appears to have reversed the damage on those files, however the pop-ups still continue.

    I ran Sucuri’s malware scanner, but it found no infections.

    Thread Starter DJChupa13

    (@djchupa13)

    Hey huntz, thanks for the reply.

    Problem 1: I probably should have looked a little bit harder for a plugins folder, lol. Found it. Uploaded Jetpack and activated. That’s one problem solved (or worked around, I guess).

    Problem 2: I currently have McKinley active. The same problem also appeared while using Crawford, so I doubt it’s the theme. To make sure, I activated Twenty Fifteen and ran PageSpeed Insights again, but I’ve still got the same pop-ups.

Viewing 15 replies - 1 through 15 (of 16 total)