# The specified Bucket does not exist (yes again) and no --verbose **URL:** \ **Category:** Serverless Framework\ **Created:** [May 31, 2018, 9:08pm UTC](https://forum.serverless.com/t/the-specified-bucket-does-not-exist-yes-again-and-no-verbose/4626 "2018-05-31T21:08:34Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![logemann](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/logemann/32/1885_2.png) [@logemann](https://forum.serverless.com/u/logemann)\ **Post date:** [May 31, 2018, 9:08pm UTC](https://forum.serverless.com/t/the-specified-bucket-does-not-exist-yes-again-and-no-verbose/4626/1 "2018-05-31T21:08:34Z")
Hi, i know this topic is kind of an evergreen but i really cant get it to work and deleting the stack is not an option for me. First of all, the --verbose option doesnt work. The only thing i get on **sls deploy --verbose** is: > Loge-MBP:serverless-eu-central-1 ml$ serverless deploy -v > Serverless: Packaging service… > Serverless: Excluding development dependencies… > > Serverless Error --------------------------------------- > > The specified bucket does not exist After checking the deployment buckets (assuming the error might fail with the deployment bucket) i ve seen a difference while doing: **serverless info --verbose** : > Stack Outputs > ServerlessDeploymentBucketName: okaydocs-dev-serverlessdeploymentbucket-xxxxxxx This bucket is not listed in my s3 bucket overview. The last deployed bucket has a different name. And the cloudformation stack also tells me that its the name of the currently existing s3 bucket and not the one i get via **sls info** So i have two questions: How can i increase the verbosity to pinpoint the problem better? Why do i get a different ServerlessDeploymentBucketName as the one which was created during last cloudformation run? Where does Serverless gets this name from? Thanks ---
**Author:** ![logemann](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/logemann/32/1885_2.png) [@logemann](https://forum.serverless.com/u/logemann)\ **Post date:** [May 31, 2018, 9:49pm UTC](https://forum.serverless.com/t/the-specified-bucket-does-not-exist-yes-again-and-no-verbose/4626/2 "2018-05-31T21:49:31Z")
I figured that while --verbose doesnt work, in fact **SLS\_DEBUG=“\*” serverless deploy** does. Is this a bug? So my error is looking like that in verbose mode. (doesnt help me unfortunately): > Loge-MBP:serverless-eu-central-1 ml$ SLS\_DEBUG=“\*” serverless deploy > Serverless: Load command run > Serverless: Load command config > Serverless: Load command config:credentials > Serverless: Load command create > Serverless: Load command install > Serverless: Load command package > Serverless: Load command deploy > Serverless: Load command deploy:function > Serverless: Load command deploy:list > Serverless: Load command deploy:list:functions > Serverless: Load command invoke > Serverless: Load command invoke:local > Serverless: Load command info > Serverless: Load command logs > Serverless: Load command login > Serverless: Load command logout > Serverless: Load command metrics > Serverless: Load command print > Serverless: Load command remove > Serverless: Load command rollback > Serverless: Load command rollback:function > Serverless: Load command slstats > Serverless: Load command plugin > Serverless: Load command plugin > Serverless: Load command plugin:install > Serverless: Load command plugin > Serverless: Load command plugin:uninstall > Serverless: Load command plugin > Serverless: Load command plugin:list > Serverless: Load command plugin > Serverless: Load command plugin:search > Serverless: Load command emit > Serverless: Load command config > Serverless: Load command config:credentials > Serverless: Load command rollback > Serverless: Load command rollback:function > Serverless: Invoke deploy > Serverless: Invoke package > Serverless: Invoke aws:common:validate > Serverless: Invoke aws:common:cleanupTempDir > Serverless: Packaging service… > Serverless: Excluding development dependencies… > Serverless: Invoke aws:package:finalize > Serverless: Invoke aws:common:moveArtifactsToPackage > Serverless: Invoke aws:common:validate > Serverless: Invoke aws:deploy:deploy > > Serverless Error --------------------------------------- > > The specified bucket does not exist > > Stack Trace -------------------------------------------- > > ServerlessError: The specified bucket does not exist > at BbPromise.fromCallback.catch.err (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:272:11) > From previous event: > at persistentRequest (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:255:13) > at doCall (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:207:9) > at BbPromise (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:224:14) > From previous event: > at persistentRequest (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:205:38) > at Object.request.requestQueue.add [as promiseGenerator] (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:245:49) > at Queue.\_dequeue (/usr/local/lib/node\_modules/serverless/node\_modules/promise-queue/lib/index.js:153:30) > at /usr/local/lib/node\_modules/serverless/node\_modules/promise-queue/lib/index.js:109:18 > From previous event: > at Queue.add (/usr/local/lib/node\_modules/serverless/node\_modules/promise-queue/lib/index.js:94:16) > at AwsProvider.request (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/provider/awsProvider.js:245:39) > at AwsDeploy.getMostRecentObjects (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/deploy/lib/checkForChanges.js:33:26) > From previous event: > at AwsDeploy.checkForChanges (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/deploy/lib/checkForChanges.js:20:8) > From previous event: > at Object.aws:deploy:deploy:checkForChanges [as hook] (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/deploy/index.js:112:10) > at BbPromise.reduce (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:372:55) > From previous event: > at PluginManager.invoke (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:372:22) > at PluginManager.spawn (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:390:17) > at AwsDeploy.BbPromise.bind.then (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/deploy/index.js:101:48) > From previous event: > at Object.deploy:deploy [as hook] (/usr/local/lib/node\_modules/serverless/lib/plugins/aws/deploy/index.js:97:10) > at BbPromise.reduce (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:372:55) > From previous event: > at PluginManager.invoke (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:372:22) > at PluginManager.run (/usr/local/lib/node\_modules/serverless/lib/classes/PluginManager.js:403:17) > at variables.populateService.then (/usr/local/lib/node\_modules/serverless/lib/Serverless.js:102:33) > at runCallback (timers.js:696:18) > at tryOnImmediate (timers.js:667:5) > at processImmediate (timers.js:649:5) > at process.topLevelDomainCallback (domain.js:121:23) > From previous event: > at Serverless.run (/usr/local/lib/node\_modules/serverless/lib/Serverless.js:89:74) > at serverless.init.then (/usr/local/lib/node\_modules/serverless/bin/serverless:42:50) > > Get Support -------------------------------------------- > Docs: [docs.serverless.com](http://docs.serverless.com) > Bugs: [Issues · serverless/serverless · GitHub](http://github.com/serverless/serverless/issues) > Issues: [forum.serverless.com](http://forum.serverless.com) > > Your Environment Information ----------------------------- > OS: darwin > Node Version: 10.0.0 > Serverless Version: 1.27.3 ---
**Author:** ![logemann](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/logemann/32/1885_2.png) [@logemann](https://forum.serverless.com/u/logemann)\ **Post date:** [May 31, 2018, 10:07pm UTC](https://forum.serverless.com/t/the-specified-bucket-does-not-exist-yes-again-and-no-verbose/4626/3 "2018-05-31T22:07:52Z")
Yikes. I found the problem. Someone killed my accesskey on AWS and created a new one. So it was basically a security issue but of course the error message didnt reported properly. **To the devs: Would it be possible to present a better error than “Bucket does not exist” for an auth problem like this ?** This is misleading at best. Would have saved me 3 hours. Thanks Marc