Support

Home Forums Event Espresso Premium HTTP ERROR 500 (3)

HTTP ERROR 500 (3)

Posted: February 21, 2017 at 2:46 am

Viewing 9 reply threads


SubZeroie

February 21, 2017 at 2:46 am

Morning Support,

I appear to be having this http error 500 again on my site.

I have confirmed my Memory has been increased to 256mb.

The same issue is happening again. could you shed any light on this for me please.

Also i found when i updated to the latest WP this error got worse so i rolled back.

Could it be possible EE4 is not compatible with the latest WP?

Below is a link to my last tread on this issue.

https://eventespresso.com/topic/http-error-500-2/

Thanks, Rob


Tony

  • Support Staff

February 21, 2017 at 3:41 am

Hi Rob,

Have you followed the same steps as last time? Enabling WP_DEBUG and catching the error?

‘Error 500’ just means there was an error and does not show the cause so we need to full error to see what is happening.

Could it be possible EE4 is not compatible with the latest WP?

We always test EE against the most recent version of WP so this is unlikely.


SubZeroie

February 21, 2017 at 4:59 am

Thanks Tony for getting back to me. I cant apply the WP_DEBUG until later today when i am home with access to FTP. I was able to access the log file off my CPanel, below are the last few entries.

[21-Feb-2017 09:30:14 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 13225309 bytes) in /wp-includes/wp-db.php on line 1171
[21-Feb-2017 09:38:59 UTC] PHP Deprecated:  Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set 'always_populate_raw_post_data' to '-1' in php.ini and use the php://input stream instead. in Unknown on line 0


Tony

  • Support Staff

February 21, 2017 at 5:34 am

That’s fine, we only need the errors (which the log provides) however we don’t need the same error repeated several times so I’ve removed most of them from your reply.

[21-Feb-2017 09:30:14 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 13225309 bytes) in /wp-includes/wp-db.php on line 1171

You’re site is still running our of memory, you’re using 256MB of ram currently and you site requires more.

Are you using a visual builder on the site?

[21-Feb-2017 09:38:59 UTC] PHP Deprecated: Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set ‘always_populate_raw_post_data’ to ‘-1’ in php.ini and use the php://input stream instead. in Unknown on line 0

That one can is a depreciation notice which you will continue to see util you follow the instructions provided in the notice (or request your host do that for you). Its not related to the errors your seeing on the site.


SubZeroie

February 21, 2017 at 6:48 am

Sorry about that Tony. Just a little puzzled over it all. When i check to see what memory is in use it is only telling me 92mb, so i should have plenty of space left i would have imagined.

Would I be best hosting EE4 on its own separate WP account on a sub-domain maybe or what would be your suggestions?


Tony

  • Support Staff

February 21, 2017 at 7:00 am

When do you see the error 500 on the site?

When i check to see what memory is in use it is only telling me 92mb, so i should have plenty of space left i would have imagined.

That value is for that specific request you just made, where are you looking at that memory value?

Would I be best hosting EE4 on its own separate WP account on a sub-domain maybe or what would be your suggestions?

That won’t make any difference, your site is using 256MB of memory and then throwing the error, the memory used is what you have set as available so the config is correct.

Is there an event I can run some test registration on to see what is happening?
Are there specific steps I need to take?


SubZeroie

February 21, 2017 at 1:33 pm

Hi Tony, it seems to be working fine now since i increased the memory to 512MB. I will keep an eye on it for now and see how it goes.

I am also going to do a full sweep of my site to make sure there was no corruption for other plugins that could be causing this. It seems to have only started happening after i upgraded WP some time back.

I am strongly thinking of rebuilding a fresh site with fresh code to eliminate this possibility.


Tony

  • Support Staff

February 22, 2017 at 4:06 am

Memory usage depends on a lot of different factors so its hard to say if there is a problem or not, although 512MB for ‘normal’ usage could be considered high.

Is this a high traffic site?


SubZeroie

February 22, 2017 at 6:22 am

No i would not consider a high traffic site at all. Currently low traffic, with the aim to increase it.


Tony

  • Support Staff

February 22, 2017 at 8:56 am

Hmm, it could be a lot of different things really, have you checked the size of the database recently? Specifically the wp_options table?

Viewing 9 reply threads

The support post ‘HTTP ERROR 500 (3)’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso