HostFission

Linux server monitoring, management & custom solutions for top websites globally. Trusted experts in software development & consulting.

[HostFission @HostFission]

Seems there was another power outage at @GorillaServers, both @eevblog's primary servers were affected.

[HostFission @HostFission]

@avar12345 @eevblog @GorillaServers Sorry yes, there has been some problems with filesystem consistency across the cluster which we are resolving. Site is back up, but there may still be some intermittent outages as we continue to work on resolving this.

[HostFission @HostFission]

@TheSkepticalSc2 @eevblog @GorillaServers Great question! The DC is supposed to be providing these services. Still yet to get any information on this, and follow up questions have been ignored even via the support ticket I have over the failed drive.

[HostFission @HostFission]

@HowardL3 @eevblog @GorillaServers Unfortunately it's not "new", checking the power on hours from the smart status, these drives have over 3 years of total on time. Seems @GorillaServers recycled old drives when we asked to have SSDs installed.

[HostFission @HostFission]

@eevblog @GorillaServers Services are back online, but might be a bit slow while the cluster gets back into a consistent state. Will be in touch @GorillaServers regarding the faulty SSD.

[HostFission @HostFission]

@eevblog There was a power fault for sure, our two primary servers lost power at the same time, this has caused some clustering issues which we are working to resolve now. Care to comment @GorillaServers ?

It also seems one of the new SSDs in one of the servers has failed.

[HostFission @HostFission]

@eevblog @atulresc Yes, we are having some issues with IO performance and have been working to upgrade the servers to combat this.

[HostFission @HostFission]

@eevblog @electrodacus It's back online, the cause of the outage is still under investigation however.

[HostFission @HostFission]

🔒 Protecting our clients' websites with precision! 💪 Our VPS solution collects all failed login attempts, blocking slow brute force attacks. No need for WordPress plugins. Once a malicious host is identified, our edge servers safeguard ALL our clients. #Cybersecurity

[HostFission @HostFission]

Seeking lightning-fast WordPress hosting? Experience unparalleled performance with our custom hosting stack and tailored solutions, optimized for WooCommerce. Check out our clients' success stories: https://t.co/sCPU3cqCJR

#WordPressHosting #HighPerformance

[HostFission @HostFission]

And then you get complaints from them that you send it to the wrong email contact. It's not our fault if you're putting in the wrong email address for your abuse contact, and you misuse the fields. As it goes with any database "Garbage In Garbage Out"

[HostFission @HostFission]

We run an automated service to detect, collate and automatically report IPs trying to brute force our servers to their respective abuse emails as per the whois records. There is a `abuse` field specifically for this, but you get some net-block owners doing this... Why?

[HostFission @HostFission]

This work has been completed :)

[HostFission @HostFission]

Just a heads up @eevblog and friends, we are performing some server maintenance that may result in slow load times or failure to load pages. We will let you all know when we are done :)

[HostFission @HostFission]

Just a heads up @eevblog and friends, we are performing some server maintenance that may result in slow load times or failure to load pages. We will let you all know when we are done :)

[HostFission @HostFission]

@eevblog Work has been completed and services should have returned to normal.

[HostFission @HostFission]

@eevblog @ufrat Well this is egg on my face, we do indeed have an issue with forwarding to google here. A bounce report from a properly configured system confirms it is an issue on our end. My apologies for my incorrect diagnosis here.

[HostFission @HostFission]

@eevblog @ufrat No, this is a SPF record configuration issue on the senders end, there is zero doubt as to the failure. This is not you, but them. The sender needs to have their IT department add the IP of the sending server to their SPF records.

[HostFission @HostFission]

@pneumon @eevblog Thanks, this is the first bounce that was provided that has come from a system that is properly configured. We do indeed have an issue on our side with regards to how things are being forwarded to google. @HailMingHail I am sorry, it seems you were correct with regards to the fwd

[HostFission @HostFission]

@HailMingHail @eevblog Thanks. Your email was rejected because your provider's SPF record is corrupt, and your mail server did not DKIM sign your email but your domain advertises a DMARC policy

[HostFission @HostFission]

@relluem94 @eevblog Please DM me the email you sent from, or alternatively email it to info @ https://t.co/VmeDcQ78e2 and I will check things on the server end.

[HostFission @HostFission]

@HenryMorgan75 @eevblog Dave's SPF is properly implemented as is DKIM (See: default._domainkey.eevblog.com). In both cases Dave's SPF and DKIM records have zero bearing on incoming email, only his outgoing. The issue here is incoming mail, not outgoing.