Packagecontrol.io not working?

[hhue13]

Is the site site (https://packagecontrol.io) down? Tried to install package control but failed with the following errors in the console:

— snip —
Error installing Package Control: HTTPS error encountered, falling back to HTTP - <urlopen error [Errno 11004] getaddrinfo failed>
Error installing Package Control: HTTP error encountered, giving up - <urlopen error [Errno 11004] getaddrinfo failed>
error: An error occurred installing Package Control

Please check the Console for details

Visit site/installation for manual instructions
Error installing Package Control: HTTPS error encountered, falling back to HTTP - <urlopen error [Errno 11004] getaddrinfo failed>
Error installing Package Control: HTTP error encountered, giving up - <urlopen error [Errno 11004] getaddrinfo failed>
error: An error occurred installing Package Control

Please check the Console for details

Visit site/installation for manual instructions
— snip —

Trying to access the site via a browser does not work either.

P.S: Sorry, had to use site as I’m only allowed to use 2 links

[milkman]

Currently not reachable from here, too. I am sure @wbond will have a look into it soon

[Star]

Also not reachable from here. Just gotta be patient, I’m sure it will be fixed soon.

[spacedragon]

I havent seen package control ever go down, but generally what timeframe are looking at for it come back up?

[RMP]

Yup, packagecontrol.io seems to be down which is kind of unfortunate timing for us.
Hopefully it will get fixed soon

I’m replying just to get the word out there in case the team hasn’t noticed yet

[watch]

Actually… There seems to be something more going on:

This domain was recently registered at Namecheap. Please check back later!

[Maximko]

Last packagecontrol breakdown happened in January this years, it took a day or two to restore.

[watch]

This works in the meantime:

# /etc/hosts
50.116.34.243   packagecontrol.io

Don’t forget to remove when the domain is up again

[flybynight]

This may explain things better:

Registry Expiry Date: 2019-10-15T05:30:00Z

[RMP]

Where did you get that to appear? For me it just outputs a default Chrome ERR_CONNECTION_REFUSED - with nothing in console or the network tab in inspect tools.

But that message is interesting since it says it’s been “recently registered” - http://whois.domaintools.com/packagecontrol.io .
You can see there it’s been with namecheap since 2014

Edit: nvm got comment sniped

[watch]

Only shows on http:

curl http://packagecontrol.io

[spacedragon]

It seems to be back now

[spacedragon]

and its down again

[jelek21]

I confirm it is down again, not showing either with curl on HTTP nor with the previously given IP (50.116…) for me

[neo2049]

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.

[aidlml]

http://packagecontrol.io is live now

[rhinog]

Not from here (UK) - straight to Namecheap registration advert

[wbond]

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.

[cgaillard]

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

[Remi]

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.