-
- 834 Posts
Hi,
just did a fresh install of Revo 2.2.6 trad and am getting the dreaded 500 Internal Server Error whenever I do anything in the back end.
Strange thing is it doesn't seem to be affecting anything or preventing me from doing anything, it's just annoying.
I know this has been discussed many times but I didn't come across any solutions in the other threads.
Any ideas?
Thanks
[ed. note: markg last edited this post 11 years, 2 months ago.]
Content Creator and Copywriter
-
- 24,544 Posts
Have you turned Friendly URLs on? If it's happening on every manager action, the most likely culprit is something in the .htaccess file (or the lack of one). You might try renaming the ht.access file in the Manager folder to .htaccess.
-
- 834 Posts
No, it wasn't furls, although I did double check.
Seems to be a hosting issue.
Having all sorts of problems trying to get it installed properly.
Content Creator and Copywriter
-
- 834 Posts
Turns out it was a hosting memory limitation. Have increased the memory so we'll see how that goes
Content Creator and Copywriter
-
- 24,544 Posts
Interesting. Normally, MODX won't install unless there's enough memory for it to run.
-
- 834 Posts
Bob,
here's what they told me
The reason why this is occurring is because the ModX installation is hitting the memory resource limits on your account (512MB). This only occurs when selecting specific links in the management panel.
It was easy enough to fix once they knew what the problem was.
Revo also runs a bit faster now they've upped the memory.
Content Creator and Copywriter
I can't think of any reason why MODX would be hitting up 512 megs of memory... I've had it up on shared hosts limited to 32 (and later 64) mb easily. Sounds like something else funky is going on in the background.
-
- 834 Posts
Mark H
He he, there's always something funky going on in the web. Murphy's Law.
Anyway, it's fixed now.
Content Creator and Copywriter
I would be seriously alarmed by this. It's not fixed; it shouldn't be doing that in the first place. Throwing more memory at it isn't "fixing" whatever the original problem is.
I'll agree with Mark you shouldn't need that much memory unless something is horridly wrong. Susan is right you should determine and fix the problem.