Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter coffeeandmagic

    (@coffeeandmagic)

    So, this just got weirder!

    It turns out it has nothing to do with publishing a blog post – that works perfectly fine.

    The 500 internal server error is triggered by posting a link to the blog post on Twitter! We have tried it twice now, and it happens everytime – post a blog post, load it over and over again, the site is perfectly fine! Then take the link to the post, and post it on twitter.

    The site will then get hit by twitterbots, yahoo, etc just after this and in no time, will start spitting out 500 internal server error because the web server runs out of memory.

    This is so weird, I have no idea what to look for or do now – anyone have any ideas?

    Thread Starter coffeeandmagic

    (@coffeeandmagic)

    Thanks Tara, I won’t waste time with Godaddy support, they just give you the usual “disable all plugins etc” as the host server itself is running fine it seems, it is definitely related to this particular wordpress site as it happened on the previous host too with this site (we recently moved it).

    It is a super weird WordPress problem. I will try the debugging, thanks!

    Thread Starter coffeeandmagic

    (@coffeeandmagic)

    Hi Tara, thank you for this – to address your many great ideas:

    We run the site so we have full access to wp-admin, ftp, cpanel etc etc.

    1. all plugins and themes have been disabled and enabled – problem persists

    2. Htaccess has been deleted and recreated – problem persists

    3. There are no server errors, which is so weird! The server spits out error 500 to the browser yet it logs nothing at all in the server log, nothing! So weird!

    The client just informed us today of this further development:

    “I posted 4 blog posts in a row without leaving the admin panel with no problems at all. On the 5th blog posts I posted it fine and THEN I clicked the link to the post to read the post – then I got the 500 server error and the site died for 10 minutes.”

    So it appears to be triggered NOT when posting, but when visiting this new post right after posting.

    Even weirder – the site and the new posts works perfectly fine now! The problem correct itself after 5-10 minutes.

    It is almost like the permalink to this new post does something, triggers something … I have no idea what though.

Viewing 3 replies - 1 through 3 (of 3 total)