question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error in deployment connect EACCES

See original GitHub issue

Hey, 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:closed
  • Created 7 years ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
mauricionrcommented, May 10, 2016

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

remote: Copying file: 'src\index.html'
remote: Using start-up script index.js from package.json.
remote: Generated web.config.
remote: Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.1
2.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0.
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/ee-first/-/ee-first-1.1.1.tgz
remote: npm WARN retry will retry, error on last attempt: Error: connect EACCES 199.27.76.162:443 - Local (undefined:undefined)
remote: ..........................................................................
remote: npm ERR! fetch failed https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz
remote: npm WARN retry will retry, error on last attempt: Error: connect EACCES 23.235.46.162:443 - Local (undefined:undefined)
remote: ...................................................................................................................
remote: Command 'starter.cmd "D:\home\site\d ...' was aborted due to no output nor CPU activity for 61 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this
remote: Job) if needed.
remote: starter.cmd "D:\home\site\deployments\tools\deploy.cmd"
remote:
remote: Error - Changes committed to remote repository but deployment to website failed.
To https://{user}@{webapp}.scm.azurewebsites.net:443/{git}.git
 * [new branch]      api -> api
0reactions
mauricionrcommented, May 15, 2016

Yes, solved!

Thanks!!

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found