[Question] Get 403 ERR when trying to download packages

[Jeannito]

Hi :),

When we try to deploy our app (not behind a proxy), we get a 403 ERR from npm js. Everything was alright before this morning and no big changes happened.

Is someone get this issue before?

Step 9/14 : RUN npm install
403 Forbidden - GET https://registry.npmjs.org/@material-ui%2fcore

EDIT: when we do it behind a proxy it works...
Do you think npm js could have ban our server address

[thomas15v]

I have the same issue on all my OVH servers. Looks like cloudflare has banned their entire IP range.

EDIT: locally npm works fine thought.

[flozz]

Same here, our CI piplines fail and our team members that are behind our VPN cannot install any packet anymore... ¬_¬'

[ProfessorLaw]

Hello there !

Same issue for me on all of our OVH servers. I get a 403 when trying to run npm install (or even trying to curl -v https://registry.npmjs.org ).

As said by thomas15v, it works fine locally..

[toxinu]

Same here:

*   Trying 104.16.26.35...
* Connected to registry.npmjs.org (104.16.26.35) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 592 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_ECDSA_AES_128_GCM_SHA256
* 	 server certificate verification OK
* 	 server certificate status verification SKIPPED
* 	 common name: ssl891738.cloudflaressl.com (matched)
* 	 server certificate expiration date OK
* 	 server certificate activation date OK
* 	 certificate public key: EC
* 	 certificate version: #3
* 	 subject: CN=ssl891738.cloudflaressl.com
* 	 start date: Tue, 19 May 2020 00:00:00 GMT
* 	 expire date: Wed, 25 Nov 2020 23:59:59 GMT
* 	 issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO ECC Domain Validation Secure Server CA 2
* 	 compression: NULL
* ALPN, server accepted to use http/1.1
> GET /@edx/edx-proctoring/-/edx-proctoring-1.5.0.tgz HTTP/1.1
> Host: registry.npmjs.org
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Date: Fri, 29 May 2020 08:23:10 GMT
< Content-Type: text/plain; charset=UTF-8
< Content-Length: 16
< Connection: keep-alive
< X-Frame-Options: SAMEORIGIN
< Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Thu, 01 Jan 1970 00:00:01 GMT
< Set-Cookie: __cfduid=db67e7133a6651f46451f3d478271a6f81590740590; expires=Sun, 28-Jun-20 08:23:10 GMT; path=/; domain=.npmjs.org; HttpOnly; SameSite=Lax
< cf-request-id: 03012035fe00000847e8866200000001
< Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< Server: cloudflare
< CF-RAY: 59aecfcff82a0847-CDG
<
* Connection #0 to host registry.npmjs.org left intact
error code: 1020

[dimduj]

Same error here from OVH server.
trying to reach a repo using curl and got an error 1020

curl -L https://registry.npmjs.org/@babel%2fruntime error code: 1020

[Hazmi35]

Same issue here got 403 Forbidden on all of my OVH Servers, Some mirrors like yarn registry (registry.yarnpkg.com) also get affected.

[mpangrazzi]

Same here for all our servers on OVH

[FuriousTurtle]

Same problem, cannot npm ci anymore on our build server ... we get error 403 :(

[flozz]

I tried with different OVH servers that are on different IP range... They are all blocked.

You banned EVERYONE that have OVH as Server Hoster and ISP ^^'

[flozz]

OVH is aware of the problem http://travaux.ovh.net/?do=details&id=44819

[pbe-axelor]

FYI: http://travaux.ovh.net/?do=details&id=44819

[speicus]

NPM status website reports "After a cautious period of monitoring the issue, we believe we've mitigated any user-facing impact".

https://status.npmjs.org/incidents/1mxp8z5hykx8

That is definitely not the case. Still getting 403s and waiting for OVH to fix their issue.

[Jeannito]

While you are waiting for OVH to fix it, the best temporary fix is to do it through a proxy.

npm config set https-proxy http://proxy.

It works for me

[wzrdtales]

... . I just thought it is only me. Banning a whole data center is incredibly unreasonable and unprofessional...

I understand that they don't want to pay for excessive traffic, but they also did not publish a self hosted solution for auditing to help fixing the problem...

[flawedworld]

Yep, happened to all our OVH stuff, how can you manage to ban the largest hosting provider in europe...

[benjauger]

Same here, OVH, EUW.
Workaround by using Scaleway network to proxy HTTP(S)

[flawedworld]

Same here, OVH, EUW.
Workaround by using Scaleway network to proxy HTTP(S)

LOL literally doing the same thing rn

[jmiguelsamper]

Same here, we have several OVH servers and we are getting 403 Forbidden errors for any call.

[dimduj]

FYI: Ovh is aware of the issue : http://travaux.ovh.net/?do=details&id=44819 Regards

[odura]

Same here (OVH Server)

npm http fetch GET 403 http://registry.npmjs.org/cross-env 67ms

[klijakub]

We have the same problem (OVH servers)

[lumaxis]

Hey everyone! Apologies for the issues earlier today.
We just made some changes, can someone please confirm if you are still seeing these 403 errors?

For additional info about npm's status, you can also refer to our status page at http://status.npmjs.com/

[klijakub]

Fixed ;) Thanks!

[ProfessorLaw]

Hello @lumaxis
I just tried on one of my OVH servers and it seems to answer properly now. Thanks !

[lumaxis]

Awesome, thanks for confirming 🙏🏼

I'll keep this issue open for a little bit longer for visibility and close later. Feel free to post again here or reach out to our support via https://www.npmjs.com/support

[pbe-axelor]

@lumaxis Same here, no more errors from the OVH network.
Thx

[Iliyass]

Fixed for me 👍
Thanks

[flozz]

Works here, thanks! :)

[flawedworld]

Working great for us now. Will keep a close eye on it. Big Thanks! :D

[mpangrazzi]

Fixed also here, thank you :)