Can't make initial connection to WordPress.com?

  • Author
    Posts
  • #1067938

    verycunning
    Member

    I checked the debug.log today and found it had some data, but only related to akismet. (was set to 777). Today I also set to “1”: @ini_set(‘display_errors’,1);

    Full data from debug.log:

    [22-Nov-2012 00:06:38] PHP Notice: Undefined index: HTTP_REFERER in /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-content/plugins/akismet/akismet.php on line 323

    [22-Nov-2012 00:06:41] PHP Warning: Cannot modify header information – headers already sent by (output started at /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-content/plugins/akismet/akismet.php:323) in /services10/webpages/s/p/sportsactivitymd.com/public/blog/wp-trackback.php on line 20

    Paul

    #1067939

    verycunning
    Member

    I also downloaded jetpack 2.0.2, does not resolve issue.

    #1067940

    kathrynwp
    Staff

    Hi there, sorry this is still giving you trouble.

    Could you please confirm that your Site URL and WordPress URL are both set to http://www.sportsactivitymd.com/blog – exactly that, with no trailing slash – under Settings > General?

    #1067941

    verycunning
    Member

    Hi. Yes that is exactly how they are set. Thank you for following up.

    #1067942

    kathrynwp
    Staff

    When you say that you couldn’t run the compatibility test because “it fails in an identical fashion” could you please let me know exactly what that means? Are you able to activate the compatibility plugin alright? Do you see an Internal Server Error at some point during the test, and exactly when does that happen?

    #1067943

    verycunning
    Member

    I am able to activate the compatibility test, that causes no error.
    On clicking “Jetpack Compatibility TEST” (left navigation), the page goes blank (loads http://www.sportsactivitymd.com/blog/wp-admin/plugins.php?page=jetpack-compatibility-test) and the page display is:
    (Title:) 500 Internal Server Error
    (Page content:) Internal Server Error

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

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

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

    (end)

    I never see anything that would allow me to perform the compatibility test itself (configure parameters, start, etc.)

    #1067944

    kathrynwp
    Staff

    Could you please test whether you’re are able to run another plugin? Would you mind trying to install and activate any other plugin of your choice and let me know if you get it working.

    So far, no plugins have run without some sort of error, is that right? Jetpack won’t connect, the compatibility test doesn’t work, and Akismet shows errors in your log. If you aren’t able to successfully run any plugins on the site, it seems likely there’s a configuration issue on your server, which your host would be best placed to diagnose.

    #1067945

    verycunning
    Member

    Akismet does show those two lines, but functions correctly. I have a couple of other plugins I can try.

    Is there possibly a debug version of the compatibility test plug in, or could we include a BREAK in it for diagnosis?

    I’ll report back after I try another plug in.

    #1067946

    verycunning
    Member

    I am able to successfully install and activate these two plugins:

    Facebook (official) 1.1.5 (current version)
    Twitter Widget Pro 2.4.1 (current version)

    The appear to function correctly, that is, I can access their configuration pages.

    #1067947

    kathrynwp
    Staff

    Thanks for testing this. I’ve brought this to our developer team for further investigation and will keep you posted.

    #1067948

    verycunning
    Member

    thanks!

    #1067949

    kathrynwp
    Staff

    One thing you could try is increasing the amount of memory allotted to PHP on your installation:

    http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    Depending on your server setup you may need to ask for your host’s assistance, as not all hosts allow memory to be increased using this method.

    Let me know if this helps.

    #1067950

    verycunning
    Member

    I set to 96M, per your message. No change.
    (phpinfo reports for PHP core: memory_limit 128M)

    Can you tell me if this escalation is in an “active” queue? That is, can you estimate when someone will look at this issue (days, weeks, months)?

    Thanks.

    #1067954

    kathrynwp
    Staff

    Thanks for trying this. Since this didn’t work, I’ve asked our developers to have another look at your case.

    #1067955

    kathrynwp
    Staff

    Unfortunately the Jetpack developers have confirmed that we are unable to troubleshoot this any further on our end. Internal server errors are host-side issues that can’t be solved without knowing the cause, which we can’t do without seeing your error logs. If your host won’t provide them or help you figure out what’s causing the server error, you might want to consider switching hosts if Jetpack is essential for the site.

    I’m very sorry we couldn’t resolve this for you.

    #1067957

    verycunning
    Member

    That is unfortunate, and an unfortunate position to take. Since the error is unique to Jetpack, I would expect WordPress to take more interest in it. Apparently though, no one else is reporting this problem, so in that sense I understand the difficulty in prioritizing this failure.

    Of course I am also disappointed with the host, but they were previously selected by the client, so that is another issue. It may indeed be that I need to switch hosts, or at least host the WordPress portion on a different host.

    Nevertheless, I thank you personally for your followup on this (as yet) unresolved issue.

    #1067958

    kathrynwp
    Staff

    That is unfortunate, and an unfortunate position to take. Since the error is unique to Jetpack, I would expect WordPress to take more interest in it.

    We are actually very interesting in solving this issue, but unfortunately we need the server error logs in order to do so. If you ever manage to get those from the host, we’d be glad to take another look. Please start a new thread if that’s the case, linking back to this one.

    Nevertheless, I thank you personally for your followup on this (as yet) unresolved issue.

    You’re very welcome.

    #1067959

    verycunning
    Member

    The problem seems to be resolved. (yay!)

    I was editing the .htaccess file to include the following (to track php errors)

    # Catching PHP errors:
    php_flag register_globals off

    php_value error_reporting 2047
    php_value display_errors true
    php_flag display_startup_errors true
    php_flag track_errors true

    php_flag display_errors on
    php_value error_reporting 7

    And found the following code present, which I commented out as follows:

    # php_flag display_errors on
    # php_value error_reporting 6143
    # Action php-cgi /cgi-bin/php4
    # AddType application/x-httpd-php .php
    # AddHandler php-cgi .php .phtml .php3

    # Zend Optimizer htaccess handlers#
    # AddHandler ZendOptimizer .php
    # Action ZendOptimizer /cgi-bin/php-cgi-Oct-31-2011
    # End of Zend Optimizer htaccess handlers#

    I was then able to connect and login into wordpress.com.

    I can’t say for sure where this code came from. I will leave this open for another day, and then it can be marked resolved. Thank you.

    #1067960

    kathrynwp
    Staff

    I’m very glad to hear it! Thanks for letting us know what you did to solve the issue. I’ll let the Jetpack team know in case it helps others in the future.

The topic ‘Can't make initial connection to WordPress.com?’ is closed to new replies.