Just had a 500 internal server error.
#Not-a-network issue
That is my default response to the people who report this to us in the network team
Last edited:
Just had a 500 internal server error.
No need yet. Just overclock it.I honestly just think we've finally outgrown that old Pentium III. Maybe time to consider an Athlon XP?
#Not-a-network issue
That is my default response to the who report this to us in the network team
500 Internal Server Error
nginx/1.14.1
SOP for both Networks and DBAs this![]()
LOLI got a 500 error earlier.
It showed the server is using nginx/1.14.1, which was end-of-lifed 6 years ago (https://endoflife.date/nginx). Probably want to update that...
You should also probably hide the nginx version, because, security. https://nginx.org/en/docs/http/ngx_http_core_module.html#server_tokens
LOL
Nginx 1.14 is the base version in *EL 8.x and is fully supported for security patches until at least 2029. An enterprise server OS won't be following mainline software versions or subject to their EoL dates. That's the EoL from Nginx (the company/project) not the date it stops being supported by distro(s). OcUK is safe from upgrades for a few years yet. Edit: Debian Buster (oldoldstable) also runs that version, and is also receiving security patches (ELTS) until 2029. I'm sure one of the old Ubuntu LTS is in a similar boat also.
@kindai you should have put it all on Alpine Edge tbh.![]()
I remember years back they archived some of the forum's biggest threads to improve stability, maybe it's time to do that again.