Need help? Check out our Support site, then


Can't make initial connection to WordPress.com?

  1. thanks!

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

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

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

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

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

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

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

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

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.