Error in deployment connect EACCES
See original GitHub issueHey, I’m trying to deploy my API to azure web app and i’m getting this error
remote: Selected node.js version 5.6.0. Use package.json file to choose a different version.
remote: Selected npm version 3.6.0
remote: Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml
remote: ...............................................................................................
remote: npm ERR! fetch failed https://registry.npmjs.org/bytes/-/bytes-2.2.0.tgz
remote: npm WARN retry will retry, error on last attempt: Error: connect EACCES 23.235.40.162:443 - Local (undefined:undefined)
remote: npm ERR! fetch failed https://registry.npmjs.org/accepts/-/accepts-1.3.3.tgz
remote: npm WARN retry will retry, error on last attempt: Error: connect EACCES 23.235.40.162:443 - Local (undefined:undefined)
remote: ...............
remote: npm ERR! Windows_NT 6.2.9200
remote: npm ERR! argv "D:\\Program Files (x86)\\nodejs\\5.6.0\\node.exe" "D:\\Program Files (x86)\\npm\\3.6.0\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
remote: npm ERR! node v5.6.0
remote: npm ERR! npm v3.6.0
remote: npm ERR! code EACCES
remote: npm ERR! errno EACCES
remote: npm ERR! syscall connect
remote:
remote: npm ERR! Error: connect EACCES 23.235.40.162:443 - Local (undefined:undefined)
remote: npm ERR! at Object.exports._errnoException (util.js:856:11)
remote: npm ERR! at exports._exceptionWithHostPort (util.js:879:20)
remote: npm ERR! at connect (net.js:843:16)
remote: npm ERR! at net.js:976:7
remote: npm ERR! at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:63:16)
remote: npm ERR! at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:82:10)
remote: npm ERR! { [Error: connect EACCES 23.235.40.162:443 - Local (undefined:undefined)]
remote: npm ERR! code: 'EACCES',
remote: npm ERR! errno: 'EACCES',
remote: npm ERR! syscall: 'connect',
remote: npm ERR! address: '23.235.40.162',
remote: npm ERR! port: 443,
remote: npm ERR! parent: 'compression' }
remote: npm ERR!
remote: npm ERR! Please try running this command again as root/Administrator.
remote:
remote: npm ERR! Please include the following file with any support request:
remote: npm ERR! D:\home\site\wwwroot\npm-debug.log
remote: Failed exitCode=1, command="D:\Program Files (x86)\nodejs\5.6.0\node.exe" "D:\Program Files (x86)\npm\3.6.0\node_modules\npm\bin\npm-cli.js" install --production
remote: An error has occurred during web site deployment.
remote:
remote: Error - Changes committed to remote repository but deployment to website failed.
To https://{usuario}@{webapp}.scm.azurewebsites.net:443/{git}.git
* [new branch] api -> api
Any ideia?
Thanks in advance!
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
connect EACCES 127.0.0.1:80 - Azure Functions - MSDN
After a deploy from Bitbucket this function started failing. No changes were made to the function that is failing. But to another function ......
Read more >Post request from Azure node.js web app to another server ...
I am getting an error problem with request: connect EACCES. However I am able to post data using postman to the same server....
Read more >Fix Docker VS Code Error: connect EACCES /var/run/docker ...
The VS Code error displayed connect EACCES /var/run/docker.sock and questioned me if Docker was actually running. I've never received this error when using ......
Read more >Troubleshoot deployment issues in Lambda
Deployment errors prevent the new version from being used and can arise from issues with ... Error: EACCES: permission denied, open '/var/task/index.js'.
Read more >How to fix this Error: spawn EACCES - Edward Beazer Blog
This error comes up when you don't have full permissions to the project folder. You want to run the chmod command in order...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I deleted the node_modules and run
npm install
again, and every thing ok,when a push the code to the local repository on azure i’ve got the same error but with a diferent package on npm
Yes, solved!
Thanks!!