-
Notifications
You must be signed in to change notification settings - Fork 12.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Font Awesome Pro network connection on Azure Pipeline #20400
Comments
@robmadole any chance this was a temporary issue with the private npm repo? Does not look like a configuration / authentication problem |
@tagliala it could be temporary, yes. Normally things like this are. @RobertFlorinDragut are you still experiencing issues? |
@robmadole Yes, I am still experiencing it today.. |
Hey @RobertFlorinDragut I'm going to alert our provider, Cloudsmith. But can you send them an email directly to [email protected]? When they see the |
Hi, @robmadole. Thanks, I sent them an email. Hopefully is going to be fixed. |
Hello, It appears that the problem encountered in the pipeline is the calling of an external web url npm.fontawesome.com for which traffic is not authorised. We have already opened traffic for npm.fontawesome.com. With this first problem solved, we now have a second blockage on dl-prd-fortawesome.cloudsmith.io [18.239.50.47] Could you list the urls and IP ranges that need to be trusted to use the library ? But the IPs received following our ping are not included (18.239.50.xx), so not sure it’s the good list. Thanks. |
Hello,
I am using Font Awesome Pro in my project and everything works well locally, with the following lines added in the .npmrc file.
@fortawesome:registry=https://npm.fontawesome.com/ //npm.fontawesome.com/:_authToken=${token}
When I try to publish my project through an Azure Pipeline, it fails with the following error:
npm ERR! network request to https://npm.fontawesome.com/@fortawesome/fontawesome-pro/-/6.6.0/fontawesome-pro-6.6.0.tgz failed, reason: read ECONNRESET
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
I have the token configured in blank but changed it to ${token} for obvious reasons.
The text was updated successfully, but these errors were encountered: