I know a 500 error isn’t very specific, & it’s likely not memory related as the sites all have 128mb – which surely should be enough in most cases?
Hi Jason,
That’s really strange. A 500 Internal Server error is indicative of the Stream servers experiencing some downtime.
Could you try again now, and let me know how you go?
Was it a 500 internal server error on your site, or in the migration window (which would be connecting to the Stream cloud)?
Hi Luke, it was the site in general (never got to the migration). I did try a fresh install of 3.0 & upon activating – got the same error. No doubt a hosting issue, but tracking it down…
That’s really odd. I wonder if it’s related to this: https://github.com/xwp/stream/issues/729 (unlikely).
Can you try with all your other plugins temporarily disabled? See if that helps?
Sure enough, it’s a plugin conflict. Did as you suggested, Stream installed & activated fine. Went to reactivate the deactivated plugins & whammo – there’s that 500 again.
Sorry, don’t have time right now to switch them all on one by one, but will do so when I do & report back. Might be a few days though.
I’m wondering if iThemes Security might be causing this, it is about the only plugin I can think of that might, & is used across all my sites…
Could be. Once you figure it out, would you mind posting it as an issue here?
http://github.com/xwp/stream/issues/new
I’d love to get a fix out with 3.0.1.
Hey Luke, I’ve found out which plugin is causing the issue – submitting to Github now.
We’ve been having a lot of problems with MainWP integrating with Stream 3. I’m reaching out to the developer.
I’ve looked into this, and discovered that it’s a problem on the MainWP end. I’ve already fixed the problem for them and sent them the fix. Just waiting for them to include it and release an update.
https://github.com/mainwp/mainwp-child/pull/6
