Ping is increasingly a poor tool for this as so many hosting providers block icmp requests at the gate. The error is hostname resolution, you could try querying some common name servers (dig and nslookup are examples of tools for this)
Yup. Btw, I get perfectly fine DNS resolution with ping on
www.subclub.org
Code:
> ping www.subclub.org
Pinging www.subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.
>ping subclub.org
Pinging subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.
Then again, I can also access the website just fine.
I notice that the server this domain is hosted on refuses all sorts of diagnostics; they're relatively restrictive and basically wayward at handling this.
I haven't tried using a VPN yet.
You could give that a shot.
The real solution is for
@xkaes to fix https.
I'm still working with the NEW host company to figure out the problem
This is a routine task for which virtually all hosting providers will have a how-to guide set up. If you have little/no experience setting these things up, it's still a routine question for them and with a little back & forth with them, it should take less than 48 hrs to fix this. If you're capable of following a user guide, it should be fixable within an hour. This is just to let you know that it's not very complicated or a daunting task. You can do this.
PS:
@xkaes while you're at it, you may consider removing the spam from the bottom of your home page.