Support » Plugin: wp-Typography » Plugin causes server internal problem, error 500

  • Resolved Debesyla

    (@debesyla)


    Hey

    When plugin is enabled, it causes internal server errors on frontend (not in /wp-admin/).

    [Sat May 19 01:04:21.536615 2018] [core:error] [pid 30259:tid 140544856463104] [client xxx.xxx.xx.xxx:29857] End of script output before headers: index.php
    [Sat May 19 01:04:29.591989 2018] [fcgid:warn] [pid 30259:tid 140544992831232] (104)Connection reset by peer: [client xxx.xxx.xx.xxx:11949] mod_fcgid: error reading data from FastCGI server

    It seems it started after my wordpress setup was copied from one hosting to another.

    I am not sure if this is plugin fault? Or my hosting? What should I do? wp-typography worked perfectly before.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author pepe

    (@pputzer)

    I would think it most likely that there is a problem with the configuration of the new hosting.

    What PHP version are you using? Is the memory_limit set high enough? Is there any output in the PHP error log (the lines you posted seem to be from the web server’s log).

    Plugin Author pepe

    (@pputzer)

    Hello @debesyla!

    Have you been able to resolve the server issue?

    Thread Starter Debesyla

    (@debesyla)

    PHP Version: 7.0.28
    memory_limit 256M

    Nothing in php error log :/

    Plugin Author pepe

    (@pputzer)

    Some avenues for further investigation:

    • Is error logging really enabled?
    • Have you checked if it is really only wp-Typography (i.e. by disabling all other plugins and switching to a default theme)?
    • You might also try to enable WP_DEBUG temporarily.

    Still, an internal server error looks like a problem with your hosting environment. PHP 7.0 should be fine.

    Thread Starter Debesyla

    (@debesyla)

    Yes, it is really enabled and it’s only this plugin. What kind of server settings this plugin needs? My hosting support are asking for this 🙂

    Plugin Author pepe

    (@pputzer)

    Nothing special, really. The mbstring extensions and PHP >= 5.6. You might try increasing the memory limit to 512M just to make sure it is not an OOM situation, but 256M should be fine in almost any circumstances.

    Are you sure there no must-use plugins or drop-ins enabled (object caching etc.)? They might be enabled by default by your hosting provider (if it’s not a “root” server).

    Another thing you could try (but with proper logging, there should be a trace in the PHP error log if there was any problem with transients caching) is clearing the cache in the in the backend.

    Plugin Author pepe

    (@pputzer)

    Also, as a blind guess, you might be triggering a PHP bug in the specific circumstances. Can you switch to PHP 7.1 or 7.2 to check for that? This looks like a core dump situation, and that should never be caused by a programming error in a script, but only by a bug in the PHP engine itself.

    Plugin Author pepe

    (@pputzer)

    @debesyla Have you been able to fix the issue?

    Plugin Author pepe

    (@pputzer)

    I assume the issue has been resolved.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Plugin causes server internal problem, error 500’ is closed to new replies.