Can't undo bad S3 external storage configuration

[jdboyd]

I tried, as a user, to add S3 External Storage, backed by Digital Ocean’s Spaces. When that happened, I got this error:

Creation of bucket "jdb-nc-s3" failed. Error executing "CreateBucket" on "https://nyc3.digitaloceanspaces.com/jdb-nc-s3/"; AWS HTTP error: Client error: `PUT https://nyc3.digitaloceanspaces.com/jdb-nc-s3/` resulted in a `409 Conflict` response:
<Error><Code>BucketAlreadyExists</Code><Message>Bucket already exists</Message><Resource>jdb-nc-s3</Resource><RequestId> (truncated...)
 BucketAlreadyExists (client): Bucket already exists - <Error><Code>BucketAlreadyExists</Code><Message>Bucket already exists</Message><Resource>jdb-nc-s3</Resource><RequestId>NotYetImplemented</RequestId></Error> Storage is temporarily not available

This appears when any user is logged in or anyone tries to use a publicly shared link. I can’t get access to any admin page. I tried to undo this by figureing out the mount id with:
nextcloud.occ files_external:list -a

Then deleting that with: nextcloud.occ files_external:delete 3
The delete seemed to work and now files_external:list -a shows no mounts, but I still get the above error. I tried rebooting the entire server, and still the above error.

At this point I’m less concerned with making S3 external work and getting back to the server working the way it was.

Thank you.

[jtr]

The delete seemed to work and now files_external:list -a shows no mounts, but I still get the above error. I tried rebooting the entire server, and still the above error.

Can you post your config? Are you sure you didn’t also configure Primary Storage or something like that?