When I (or others, I assume) navigate to my profile page, there is a 500 internal server error and a 'Down For Maintenance' page is fetched instead.
Quote by simplyjohn
Have you made any changes to your profile since all was last well? We do not have any other reports of this (yet).
Not that I can recall. For quite some time now, I could not see my own posts on my wall unless I followed someone's interaction to it. My wall was always blank for me
Another user told me that she would get the error when she scrolled down on my profile.
I can edit my profile, so I X-ed out the 'wall' section, and now I can view my profile.
I will un-X it to see what happens.
Quote by reader909Not that I can recall. For quite some time now, I could not see my own posts on my wall unless I followed someone's interaction to it. My wall was always blank for me
Another user told me that she would get the error when she scrolled down on my profile.
I can edit my profile, so I X-ed out the 'wall' section, and now I can view my profile.
I will un-X it to see what happens.
To try to be more clear, for some time now, I could make a post on my wall, save it, go back and not be able to see it, yet others could 'like' or comment on it, so they could see it.
IIRC, 'all posts' was blank for me, 'my posts' was blank for me. 'posts by others' showed that one post someone made a while back. I think those were the 3 choices for me to look at my wall.
Sorry if this is TMI
what browser do you use?
I seem to write a story on average every 1.5 years.
You might as well check them out: https://www.lushstories.com/profile/Georgia_27_8/stories
XGX
Could be something posted on your wall causing the error.
Maybe someone posted an image or a GIF file which is trying to load an external script for resizing?
Did you ever take a look at your profile using your browser's developer tools? They will show you exactly what is being loaded, from where, if anything is failing to load, and they should list any page errors.
I can take a look for you if you want to re-enable the offending profile section.
Also, you could try clearing your browser cache and cookies. Corrupted browser data can sometimes cause a 500 Internal Server Error.

Quote by Liz
Could be something posted on your wall causing the error.
Maybe someone posted an image or a GIF file which is trying to load an external script for resizing?
Did you ever take a look at your profile using your browser's developer tools? They will show you exactly what is being loaded, from where, if anything is failing to load, and they should list any page errors.
I can take a look for you if you want to re-enable the offending profile section.
Also, you could try clearing your browser cache and cookies. Corrupted browser data can sometimes cause a 500 Internal Server Error.
I was wondering if something on my wall was a problem. I cannot see my wall, but I was able to use 'Interactions - Content - Profile Status' to find every post I made on my wall and I deleted them all. I also found the single post on my wall by another user the same way (it had a video clip) and I deleted that. As far as I know, there is nothing on my Profile Status wall now. The error remains, however.
I did use the dev tools to see that I was getting a 500 Internal server error from lush. Perhaps I can look to see if I can find the culprit.
Since I get the same error with 4 different browsers, and another user reported the same error, I doubt that local browser cache has anything to do with it.
I un-hid my wall, and you can have a look to see if you get an error when looking at my profile and scrolling down to the status wall part.
Thanks!
Quote by reader909
I un-hid my wall, and you can have a look to see if you get an error when looking at my profile and scrolling down to the status wall part.Thanks!
So, your profile page immediately redirects to the maintenance page for me, without having to scroll down to the wall section. I've tried reloading it a bunch of times and recording the traffic with the network panel, but it doesn't show anything that jumps out.
The only thing I noted was a 204 No Content error, which was logged. This status code indicates a request succeeded, but the server intentionally returns no message body. The server has successfully processed the requested resource and isn’t returning any content because there’s nothing meaningful to send back.
Don't know if any of that is relevant to the redirection issue, but I don't think there's anything more that can be done from a user perspective. Over to Griffers and the Scooby Gang, I'm afraid. Sorry.
