Velero: Velero install failed (pls close)

[Berndinox]

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.
Install as explaint in docs

time="2019-07-02T16:04:48Z" level=info msg="Checking that all backup storage locations are valid" logSource="pkg/cmd/server/server.go:431"
An error occurred: some backup storage locations are invalid: backup store for location "default" is invalid: rpc error: code = Unknown desc = NoSuchKey:
status code: 404, request id: tx000000000000007c1c769-005d1b80a0-1b7a15-fra1a, host id:

[nrb]

The NoSuchKey description and 404 look to me like the bucket doesn't exist. velero install does not create a bucket for you, it must be made manually.

[skriss]

One other possibility - are you hitting this? (using <bucket>/<prefix> in the bucket field)

[Berndinox]

Hy, thanks for the fast response.

Installed via:
velero install --provider aws --bucket mybucket --secret-file ./credentials-velero --use-volume-snapshots=false --backup-location-config region=fra1,s3ForcePathStyle="true",s3Url=https://mybucket.fra1.digitaloceanspaces.com

my credentials-files:

[default]
aws_access_key_id = 123456
aws_secret_access_key = 78910

How can i find additional information on why it fails?

EDIT
I found the issue, the S3Url was wrong:

velero install --use-restic --provider aws --bucket DO-SPACE-NAME --secret-file ./credentials-velero --use-volume-snapshots=false --backup-location-config region=fra1,s3ForcePathStyle="true",s3Url=https://fra1.digitaloceanspaces.com

FRA1 has to be replaced with whatever location you are using inside DO.

-> Can be closed