[fixed] Issue with packages.meteor.com CERT_HAS_EXPIRED ? Can't deploy


#1

[I’m not 100% sure this is related to meteor and I’ll look for other possibilities]

I’m using mupx to deploy and recently this fails with:

>> => Errors while initializing project:
>> While selecting package versions:
>> error: Package version not in catalog: webpack:css 1.1.2
>> 
>> While refreshing package catalog to resolve previous errors:
>> error: Network error: wss://packages.meteor.com/websocket: CERT_HAS_EXPIRED

This seems to suggest that there is something wrong with packages.meteor.com's certificate.

Is this a known issue? Or should I look more into mupx?


#2

also getting the same issue when trying to deploy to modulus

While refreshing package catalog to resolve previous errors:
error: Network error: wss://packages.meteor.com/websocket: CERT_HAS_EXPIRED

#3

Looks like the whole meteor.com domain has an expired cert…


#4

God, cert expiry! @n1mmy @sashko


#5

wow wow wow, there seems a big bang~


#6

GitHub issues flood soon, I predict.


#7

Ah, crap. Sorry. I’m on it.


#8

Should be back now. Can someone confirm?


#9

looks good now, thanks!


#10

Yeah, back to life! :sweat:


#11

Great. Sorry about that! The new certificate was purchased and set up a last week, but apparently not fully deployed.


#12

install.meteor.com still fails


#13

still getting errors while trying to do “meteor login” on the CLI

stream error Error during WebSocket handshake: Unexpected response code: 502

Deploying seems to work fine though


#14


#15

Ok, I think I’ve fixed install.meteor.com and CLI login. Please confirm?


#16

confirmed. thanks!!!


#17

Yup, confirmed - works now!


#18

All goes well now! Thanks!


#19

Thanks @zhaoyao91 @gisliorn @laosb !


#20

No github issues due to that, cheers!