Jump to content
GreenSock

Carlos Lorca

Business https://npm.greensock.com/ registry is down

By Carlos Lorca, in GSAP. Views: 3,317

Moderator Tag

Recommended Posts

Posted

We're currently getting the same error. 

error An unexpected error occurred: "https://npm.greensock.com/@gsap%2fshockingly: connect ECONNREFUSED 104.131.8.206:443".

 

  • Like 1
Link to comment
Share on other sites
Posted

I am experiencing the same issue...

 

@GreenSock We're unable to deploy because of this issue...

Link to comment
Share on other sites
Posted

Hi all! Same issue here, we're looking into it. I'm going to ping @Cassie to see if she has a quick fix for us!

 

What I've done is copied the node_modules from another project that uses the same underlaying structure that also uses GSAP, but that only works if you've already installed GSAP once. 

Link to comment
Share on other sites
Posted
5 minutes ago, mvaneijgen said:

Hi all! Same issue here, we're looking into it. I'm going to ping @Cassie to see if she has a quick fix for us!

 

What I've done is copied the node_modules from another project that uses the same underlaying structure that also uses GSAP, but that only works if you've already installed GSAP once. 

That will not work with deploy pipelines and repos, where node_modules is not included.

  • Like 2
Link to comment
Share on other sites
Posted

Agreed, it dosen't work with us using CI/CD to build our sites.

Link to comment
Share on other sites
Posted

We have the same problem here.

Link to comment
Share on other sites
Posted

Anyone who has found a workaround to make a jenkins build pass meanwhile this is being fixed? 

Link to comment
Share on other sites
Posted

@wsqul In theory you could download the tar-ball file and reference that in you pakage.json.

Link to comment
Share on other sites
  • Carlos Lorca changed the title to Business https://npm.greensock.com/ registry is down
  • Author
Posted
1 hour ago, mvaneijgen said:

Hi all! Same issue here, we're looking into it. I'm going to ping @Cassie to see if she has a quick fix for us!

 

What I've done is copied the node_modules from another project that uses the same underlaying structure that also uses GSAP, but that only works if you've already installed GSAP once. 

Thanks for the advise but we're using devops pipelines and docker images so we need to install from scratch all dependencies. Hope they come back with a fix soon. We need to fix a few issues in our prod environment today. Murphy's law!

  • Like 1
Link to comment
Share on other sites
Posted

Looking into it folks. So sorry about this.

Paging @Prasanna

  • Like 3
Link to comment
Share on other sites
Posted

Thanks so much for reporting this everyone - I've reached out to Prasanna from PrivJS, they manage our private repo.

More information incoming. Thanks so much for you patience.

  • Like 7
Link to comment
Share on other sites
Posted

Sorry, nothing yet. I'll update this thread as soon as I know what's going on.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
Posted

Prasanna's on the case folks - there was an issue with their cloud service provider. Fix incoming!

  • Like 1
Link to comment
Share on other sites
Posted

This should be resolved now - feedback to verify would be appreciated 🤞 Fingers crossed.

Thanks so much for your patience and understanding everyone. Hugely appreciated.

  • Like 3
  • Thanks 1
Link to comment
Share on other sites
Posted

Hooray! Wonderful news. 

Link to comment
Share on other sites
  • Author
Posted

Thanks @Cassie

As I said it was Murphy's Law!! Just when we got a workaround to deploy our apps it's online again :D

 

Just for you to know, if you're using dockers to deploy your apps, you can use the latest docker publish image to run the dockerfile and it will work because this one already has all the node_modules needed from gsap.

:)

  • Like 3
Link to comment
Share on other sites
Posted
17 minutes ago, Carlos Lorca said:

As I said it was Murphy's Law!! Just when we got a workaround to deploy our apps it's online again :D

If you hadn't found a workaround it would probably still be broken right? I guess thanks is in order 😂

Link to comment
Share on other sites
Posted

@Cassie got it to work but now I'm getting the same issue again, is it down again? 

Link to comment
Share on other sites
Posted

Hey @Marco B. and @Raymall Perez,

 

I just created some simple NPM projects and was able to install all three bonus packages (simply, shockingly and business) using the .npmrc file, my token and the instructions provided in the installation docs.

 

Can you please give it another try and let us know?

Thanks!

Link to comment
Share on other sites
Posted

Seems fixed at our end 👍

 

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
Login Create Account