@DreamHostCare Help! Our server at 208.97.155.96 is offline! No web, can't ping, can't SSH. I work on the site, but don't have access to the DH panel to open a normal trouble ticket. Worse, my client is trying to give a presentation on our work right now!
@dhstatus Same problem. I use gmail to fetch my mail from my DH-hosted domain. I'm apparently POPping mail just fine, but SMTP connections are immediately rejected, I can't send mail. I'm disturbed that https://t.co/HA1rMA6or6 doesn't show that there's a problem.
Customers! If you're using the OceanWP theme and you see there's an update available for the Ocean Extra plugin, please update the theme first before the plugin to avoid it crashing your site. Please raise a support ticket if you have questions or need help 💜
If you’re running Elementor we suggest waiting a little bit before upgrading to the latest version. We’ve had to roll back Elementor updates for many customers today. We have seen this on WordPress 6.0.1 but it may affect other versions too.
FYI, the DNS issue with #clockingit is resolved, so it should work normally now. It would be very comforting to hear what happened and what was involved in fixing it. @fudgie, thank you for taking care of this (assuming it was you), and I sincerely hope that all is well with you
This issue with #clockingit feels different. Besides the technical stuff looking different, no one else on Twitter seems concerned. Did I miss a memo somehow? If anyone can enlighten me, I'd very much appreciate it. @fudgie feel free to DM me if that makes more sense.
@fudgie As @capile says, the #clockingit server is actually still running, you can step around the DNS problem to get to it. A bit more detail: https://t.co/IlWlEdU1Dd If you don't know how to do this, search the web for "[your operating system] hosts file". DM me if still lost.
@iManui@Erebuss I had an issue with this as well. I believe it was because of the change to the LetsEncrypt root certificate. wget on my workstation worked fine, but I think on a server I'm using it hasn't been updated recently.
@cwage@jwage I'm seeing it too. On a ping to my droplet (from my workstation, connected to Comcast): 51 packets transmitted, 38 received, 25% packet loss. Did this happen sometime recently?
@SiteGround Ah, it did not occur to me that the .tar "file" might have been a folder. Sorry! But still, that's not standard, and .tgz is definitely a common extension. I recommend you fix it, but either way I'll know what to do next time. Thank you for the reply!
@SiteGround In the new File Manager, I was unable to extract a .tgz file. I changed the name to .tar.gz, and then it worked, but it became a .tar file, which I couldn't extract. I repackaged it my stuff as a .zip and uploaded again. But surely you want to support tar..?