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.

Deployment fails with "Not Found" error

See original GitHub issue

When trying to deploy I get this:

Error --------------------------------------------------

  Error: Not Found

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Stack Trace --------------------------------------------

Error: Error: Not Found
    at filArgs.reduce (node_modules/serverless-google-cloudfunctions/provider/googleProvider.js:67:33)
    at JWT.OAuth2Client._postRequest (/node_modules/google-auth-library/lib/auth/oauth2client.js:402:3)
    at postRequestCb (node_modules/google-auth-library/lib/auth/oauth2client.js:362:12)
    at Request._callback (node_modules/google-auth-library/lib/transporters.js:106:7)
    at Request.self.callback (node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request.<anonymous> (node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage.<anonymous> (node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:188:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickDomainCallback (internal/process/next_tick.js:128:9)
From previous event:
    at PluginManager.invoke (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/classes/PluginManager.js:242:22)
    at PluginManager.run (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/classes/PluginManager.js:261:17)
    at variables.populateService.then (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/Serverless.js:99:33)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)
From previous event:
    at Serverless.run (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/Serverless.js:86:74)
    at serverless.init.then (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/bin/serverless:39:50)

Issue Analytics

State:
Created 6 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

29reactions

rdevcommented, Aug 31, 2017

@pmuens I figured it out. The problem was indeed on Google’s side. I went to Cloud Console > Deployment Manager, deleted all deployments created by Serverless and deleted respective storage buckets and deployment with previously failing service name ran successfully.

0reactions

mabuaishacommented, Feb 13, 2020

@rdev That solved my issue, Thanks 😃

Top Results From Across the Web

Deployment failed 404 not found | OutSystems

Exception: The remote server returned an error: (404) Not Found. System. InvalidOperationException: Deployment failed: Deployment failed. Could not invoke ping.

Deployment not found · Issue #2251 - GitHub

occurs when changing config to enable FUNCTION_WORKER_RUNTIME bool using portal when I am also updating the new code from vs code. Action: ...

Deployment fails immediately: file not found - Render community

We usually see this error if the “Root Directory” option is set incorrectly. The majority of projects don't need to have a value...

Troubleshoot common Azure deployment errors

Error code Mitigation More inform... AccountNameInvalid Follow naming guidelines for storage accounts. Resolve erro... AccountPropertyCannotBeSet Check available storage account properties. storageAcco... AnotherOperationInProgress Wait for concurrent operation...

[Support Guide] I've deployed my site but I still see "Page not ...

Some images producing 'failed to load resource' error on Netlify build. 404 Not Found after deploy. ReactJS SPA Reload Page Fails. Getting 404...