SSL cert expired a couple hours ago. (Time now is 11:08 AM EDT.)
New firefox just gave me this:
Also something with the SSL security...
Chrome this morning has also told me the SSL certificate is not valid.
We may have to wait for the working day in Australia to start before it will be fixed.
There are 2 servers with a load balancer, one has an expired certificate and the other is still valid till the end of October. Which server you get depends on the dice in the load balancer.
There are 2 servers with a load balancer, one has an expired certificate and the other is still valid till the end of October. Which server you get depends on the dice in the load balancer.
You are correct, one of the server had faulted and was not renewing it's certificate. This has been corrected.
one of the server had faulted and was not renewing it's certificate. This has been corrected.
Yet Chrome is still displaying a Not Secure flag.
Same result with a manual refresh or F5 refresh.
one of the server had faulted and was not renewing it's certificate. This has been corrected.
Yet Chrome is still displaying a Not Secure flag.
Same result with a manual refresh or F5 refresh.
Your end sorry mate, I just double-checked that both servers are using valid certificates now.
Edit: Note, not-secure is different to an invalid certificate. You may be trying to access resources over `http`, make sure you're hitting the site over `https` and nobody has embedded any non https content on the page you're on.
one of the server had faulted and was not renewing it's certificate. This has been corrected.
Yet Chrome is still displaying a Not Secure flag.
Same result with a manual refresh or F5 refresh.
Your end sorry mate, I just double-checked that both servers are using valid certificates now.
Edit: Note, not-secure is different to an invalid certificate. You may be trying to access resources over `http`, make sure you're hitting the site over `https` and nobody has embedded any non https content on the page you're on.
Yep all good, thanks. Definitely faster browsing and loading pages now.
Your end sorry mate, I just double-checked that both servers are using valid certificates now.
Edit: Note, not-secure is different to an invalid certificate. You may be trying to access resources over `http`, make sure you're hitting the site over `https` and nobody has embedded any non https content on the page you're on.
With Chrome, if you insist on a "not secure" connection after an invalid certificate message, Chrome will remember that setting for several hours before trying again. You have to force Chrome back to an https connection manually if you don't want to wait. The best way to do that seems to be to close the current tab and then open a new one.
Absolutely beseiged by 502s today, is one or more of the servers suffering from a stroke, or just a lack of timely whipping?
Investigating, I was alerted to this about an hour ago, seems something is causing high I/O load.
Yup, it's that thread... thanks for that, looking for the dud file.
Yup, it's that thread... thanks for that, looking for the dud file.
Was working fine late PM yesterday NZ time and I think another file was added overnight to an existing post that caused the issues.
Yup,
Issue fixed, another windows bitmap uploaded with a png extension. SMF goes nuts trying to load it and just hangs consuming tons of RAM.
Who's posting nonsense like that?
I replied to them in the thread
Thanks for the fix. Good old SMF, chainsaws round the edges.
Issue fixed, another windows bitmap uploaded with a png extension. SMF goes nuts trying to load it and just hangs consuming tons of RAM.
Ouch. Programs like SMF should not blindly trust file extensions, they should look inside the file to determine (or verify) the actual type of content.
Oh it certainly is, but it's not something that can be fixed easily.
SMF is dumb and just allows you to upload any file, and when it's an image attempts to create a thumbnail at render time (not at upload time), not only does this mean that multiple concurrent page loads will try to generate the thumbnail at once, if there are multiple images on the page, it will do them all at once (which can be slow) and cause a timeout, preventing the database from being updated with the information about the thumbnails.
The core workflow is very broken and fixing it will require overhauling how things work here. Such a "fix" would make SMF incompatible for future updates/upgrades.
At least the previewer should be fixed not to choke on malformed PNGs.
Is it exploitable for RCE too?
I did add some idiot checks for this some time back but upgrades to SMF and/or modules have undone it. I will schedule some time to investigate and re-instate what I can.
I am not sure if it's a RCE issue, IIRC it's the thumbnail preview feature which I think is an "addon" (if you can call SMF addons 'addons', more like diffs/patches)
......Never ! 