• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Main site header and image issue

rudedog

rudedog

[H]ard|Gawd
2FA
Joined
Dec 23, 2004
Messages
1,157
The front page is throwing some errors this am (6:48 am EST)

Connection failed: SQLSTATE[08006] [7] server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. could not send SSL negotiation packet: Broken pipe
​
Using two different browsers FF and Chrome via OSX on ATT fiber. Rest of the page loads just not the header and images. no ad blocker.

43349890444_b03f07d6c3_z.jpg
 
Quick follow up same issue on a Windows 10 laptop via Verizon MiFi
 
The whole page is broken when I tried reading the new Threadripper review. That error message is all you see.
 
every article in the News section seems to have that error when I click on the link...
 
Good morning all, Kyle sorry to say the error is back on the main page.
 
Yep. Just checked now. The main page is still puked.
 
Confirmed.. It's back.. :(
Connection failed: SQLSTATE[08006] [7] server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. could not send SSL negotiation packet: Broken pipe
 
Sadly still down for me, but at least I can ping it.
ping www.hardocp.com

Pinging www.hardocp.com [54.39.18.45] with 32 bytes of data:
Reply from 54.39.18.45: bytes=32 time=91ms TTL=49
Reply from 54.39.18.45: bytes=32 time=91ms TTL=49
Reply from 54.39.18.45: bytes=32 time=90ms TTL=49
Reply from 54.39.18.45: bytes=32 time=89ms TTL=49

Ping statistics for 54.39.18.45:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 91ms, Average = 90ms
 
Navilor said:
Sadly still down for me, but at least I can ping it.
ping www.hardocp.com

Pinging www.hardocp.com [54.39.18.45] with 32 bytes of data:
Reply from 54.39.18.45: bytes=32 time=91ms TTL=49
Reply from 54.39.18.45: bytes=32 time=91ms TTL=49
Reply from 54.39.18.45: bytes=32 time=90ms TTL=49
Reply from 54.39.18.45: bytes=32 time=89ms TTL=49

Ping statistics for 54.39.18.45:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 91ms, Average = 90ms
Click to expand...
Hmmm. Fine for me, can you give me a tracert?
 
We moved to new servers not too long ago, and this looks to be an issue on their end...actually not our fault for once. :) If you see ANY of this issue, please keep reporting those here!!!
 
You must log in or register to reply here.
Back
Top