It seems to be back now
Packagecontrol.io not working?
I confirm it is down again, not showing either with curl on HTTP nor with the previously given IP (50.116…) for me
Packagecontrol, as far as I know, is run on linode.com. Their status page shows that they’re doing maintenance fixing a bug. https://status.linode.com/
I guess we can just sit tight and wait.
When the server went down last January it was due to database corruption and I had to rebuild the server and manually hex-edit corrupted pages on the disk to get things back up and running, hence it being down for a day or two.
Since then the server config has been moved to ansible, built fresh on top of Ubuntu 18.04, daily whole-VM snapshots happen, and a few other improvements. We shouldn’t be looking at such a long outage again in the future.
This outage was due to registration issue - I had another domain expiring on October 16th, and I confused the renewal reminder for packagecontrol.io (on Oct 15th) with the other domain. I’ve now switched the domain to auto-renew so this doesn’t happen again.
Sorry for the issue - everything should be back online shortly.
My proxy settings doesn't work on ST3
Packagecontrol.io is not accessible in Russia
Hey @wbond
We’re still on ERR_CONNECTION_TIMED_OUT … Or the site is down again ?
I can’t connect to it since this morning (in France), for maybe 4 hours.
Looking forward to understand when i can install a new package …
Thank you
Same in midwest US. It’s popped up as blocked by a Cisco security check (corporate IT tool). I assume it’s something to do with domain security certificates and propagation speed though.
Browser now brings up the page and the manual installation worked as I could download the sublime-package and furthermore I can install packages now as well. Thanks!!
Checking DNS propagation for the domain https://dnschecker.org/#A/packagecontrol.io
I’ve found the ip that is working, as a workaround I’ve temporarily set it up in my hosts file locally until it works from everywhere. HTH
PS: Now DNS is working but I’ve needed to flush DNS cache to get it working again faster.
This is still down.
My browser can’t bring up the page because of bad CERTS:
Your connection is not private
Attackers might be trying to steal your information from packagecontrol.io (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
I just checked, the certificate expires in November (@wbond hint hint … sorry ahem.)
Just flush all your caches and/or use a faster DNS server (like Google’s 8.8.8.8
or CloudFlare’s one.one.one.one
)
Still down for me. I can ping the server properly, but nothing on 80 / 443 ports =(
There was a short outage today when the nginx/stable ppa upgraded nginx from 1.14 to 1.16. Apparently Nginx 1.16 has a segfault issue in some configurations when using a Lua worker init file, which the Package Control server does. Everything is back online now.