500 server error

  • Resolved qwik3r

    (@qwik3r)


    5 years, 2 months ago

    Getting the following error when I initiate the plugin, any ideas?

    [Mon Sep 09 23:22:05.929380 2019] [core:alert] [pid 32649] [client ] .htaccess: ‘ExpiresDefault access plus days’: bad expires code, numeric value expected <num> ‘days’, referer: options-general.php?page=ffe_plugin_options

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    Hi,

    Getting the following error when I initiate the plugin, any ideas?

    Are you talking about enabling the plugin without any settings or when you save the settings in the plugin, you receive this error?

    What PHP version is running in your server? What WordPress version are you running in your site?

    Kind regards

    Thread Starter qwik3r

    (@qwik3r)

    This was when I saved the settings. I realized the error had to do with the fact that it wrote to the .htaccess file without actually including any date. It just said (paraphrasing) “such and such expires _ days”.

    On another note, I saw your comment about this not working with nginx. I’m on wpengine and supposedly they use a dual server setup that uses both nginx and apache as there is a .htaccess file.

    Anyway, even after updating the .htaccess file to include the dates, then running it through gtmetrix I was still seeing “no expired headers” error so I suspect that it didn’t do anything anyway.

    Plugin Support mbrsolution

    (@mbrsolution)

    Hi,

    I’m on wpengine and supposedly they use a dual server setup that uses both nginx and apache as there is a .htaccess file.

    Can you speak to wpengine support. I am curious to know why it is not working in your site.

    Thank you

    Thread Starter qwik3r

    (@qwik3r)

    I’ll reach out, thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘500 server error’ is closed to new replies.