You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fact, there is a uniqueness constraint on domain name, for all users (the NO_AUTH account is a real, special, user). So, this error appears because the domain already exists in the database. As it is not displayed here, it is necessarily registered for another user.
In order to solve the issue, you can use the administrative interface with ./hadmin.sh [route] [opts] (or docker exec -it happyDomain_ctr_name hadmin [route] [opts]):
./hadmin.sh /api/domains
This will show you all the registered domains on your instance.
Then you can delete a domain with its id:
./hadmin.sh /api/domains/012345678abced -X DELETE
It should print true. And you should then be able to register your domain with the NO_AUTH account.
In the future, we'll eventually use another DB schema (with ACL on domain, to share a domain between several account), and get ride of this unwanted limitation. I don't think we'll plan to change the uniqueness behavior in the current schema.
I see advantages to having the uniqueness - altho two separate admins working independently is also a likely scenario. Just need to ensure fresh data, which can take a long time to pull in with some providers :/
For whatever reason, e.g. incorrect auth details to a provider, it's possible to get stuck here:
(trimmed out the name in the add field for security)
The text was updated successfully, but these errors were encountered: