On 16/03/2017 at 04:12, xxxxxxxx wrote:
Hey guys,
Whenever I do a search I get this on clicking the Search button:
"The page cannot be displayed because an internal server error has occurred."
It's been like this for a couple of days now. Could you sort it out please? The search function is essential on this site.
Thanks,
Steve
On 16/03/2017 at 06:05, xxxxxxxx wrote:
Hi Steve,
I'm sorry you are having problems with the search. Actually I use it all the time and never had any issues with it. But, we also encountered several times, when the entire forum was off. This is already being researched.
Can you give us some more details? Which browser on which OS are you using? Are there certain times this is happening? I mean, you say since a couple of days, but is it a certain daytime you use search or all 24 hours?
Again, sorry for any inconvenience caused. We hope to be able to sort it out as soon as possible.
On 16/03/2017 at 06:38, xxxxxxxx wrote:
I use Firefox but it shouldn't make any difference if it's a server error. Unfortunately the message doesn't give an error number, IIRC an internal error is often an Apache 500 error but there's nothing to confirm that. OS is windows 8 but again it shouldn't affect this error.
I tried several searches yesterday at different times, both day and night, with the same result, and again this morning, so it's unlikely that it's due to server overload unless someone is doing a DoS attack on your server.
Steve
On 16/03/2017 at 07:12, xxxxxxxx wrote:
I can confirm this behavior for this morning.
Don't know if you have logs. But I don't use oftenly the build-in function and I was searching around (11am in France so I guess it's the same time than your) for "quicktab" so it should be easy to find if you got them.
But As spedler said it's an apache error caused by overloading. But maybe the tomorrow maintenance will fix it? :)
On 16/03/2017 at 07:24, xxxxxxxx wrote:
Unfortunately tomorrow's maintenance has nothing to do with the server Plugin Café is running on. Sorry, to crush hopes.
Anyway, thanks for the information. And I completely agree, that server error is probably not related to your environments, but usually it's better to gather more information than too few.
I forwarded the issue to the administrator.