Error Migrating to latest php v7.4.13 on lightsail linux/bitnami

  • Resolved jdsharma

    (@jdsharma)


    3 years, 2 months ago

    Migrated WordPress using WPMigrateAll plugin from an older instance to a new WordPress instance (equivalent to the old one) using php7.4.13- Lightsail Linux/bitnami

    However, if Jetpack is active, then when we try to edit a page, we get an internal error:
    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator at you@example.com to inform them of the time this error occurred, and the actions you performed just before this error.

    More information about this error may be available in the server error log.
    —
    [Thu Feb 11 04:52:52.732484 2021] [substitute:error] [pid 1107:tid 139881195837184] [clien
    t 67.184.130.93:49816] AH01328: Line too long, URI /wp-admin/post.php, referer: https://zz
    organic.com/wp-admin/edit.php?post_type=page
    [Thu Feb 11 04:52:52.743370 2021] [proxy_fcgi:error] [pid 1107:tid 139881195837184] (12)Ca
    nnot allocate memory: [client 67.184.130.93:49816] AH01075: Error dispatching request to :
    (passing brigade to output filters), referer: https://zzorganic.com/wp-admin/edit.php?pos
    t_type=page
    [Thu Feb 11 04:52:58.377806 2021] [substitute:error] [pid 1251:tid 139881154070272] [clien
    t 103.102.89.104:58724] AH01328: Line too long, URI /wp-admin/post.php, referer: https://w
    ww.zzorganic.com/wp-admin/edit.php?post_type=page
    [Thu Feb 11 04:52:58.378662 2021] [proxy_fcgi:error] [pid 1251:tid 139881154070272] (12)Ca
    nnot allocate memory: [client 103.102.89.104:58724] AH01075: Error dispatching request to
    : (passing brigade to output filters), referer: https://www.zzorganic.com/wp-admin/edit.ph
    p?post_type=page
    [Thu Feb 11 04:53:07.971524 2021] [substitute:error] [pid 1106:tid 139881187444480] [clien
    t 103.102.89.104:58727] AH01328: Line too long, URI /wp-admin/post.php, referer: https://w
    ww.zzorganic.com/wp-admin/edit.php?post_type=page
    [Thu Feb 11 04:53:07.972136 2021] [proxy_fcgi:error] [pid 1106:tid 139881187444480] (12)Ca
    nnot allocate memory: [client 103.102.89.104:58727] AH01075: Error dispatching request to
    : (passing brigade to output filters), referer: https://www.zzorganic.com/wp-admin/edit.ph
    p?post_type=page
    [Thu Feb 11 04:53:17.674616 2021] [substitute:error] [pid 1107:tid 139881388869376] [clien
    t 103.102.89.104:58734] AH01328: Line too long, URI /wp-admin/post.php, referer: https://w
    ww.zzorganic.com/wp-admin/edit.php?post_type=page
    [Thu Feb 11 04:53:17.674678 2021] [proxy_fcgi:error] [pid 1107:tid 139881388869376] (12)Ca
    nnot allocate memory: [client 103.102.89.104:58734] AH01075: Error dispatching request to
    : (passing brigade to output filters), referer: https://www.zzorganic.com/wp-admin/edit.ph
    p?post_type=page
    —

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    3 years, 2 months ago

    Hi @jdsharma

    I ran some tests on your site, and it seems that although your domain has a valid SSL certificate, it is still possible for one to access your site via HTTP. In fact, your visitors and search engines can use either HTTP or HTTPS to access your site.

    This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with WordPress.com, as our system does not know whether it should connect to your site via one or the other address.

    To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.

    Once that’s done, try to reconnect your site to WordPress.com once again; that should solve your issue.

    Thread Starter jdsharma

    (@jdsharma)

    3 years, 2 months ago

    The redirection is fixed, but Jetpack activation still gives out the above errors. Any other suggestions will be helpful.

    Anonymous User 3392934

    (@anonymized-3392934)

    3 years, 2 months ago

    Thank you for letting us know you’re still seeing those errors.

    As a first step, please try completely reinstalling the Jetpack plugin. If that doesn’t help, I’ve found a potential solution here that is specific to Bitnami’s WordPress stack:

    – https://community.bitnami.com/t/500-internal-server-error-i-am-a-beginner-help-me-fix-this-issue/69011/6

    Please let us know if this helps! 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error Migrating to latest php v7.4.13 on lightsail linux/bitnami’ is closed to new replies.