document ways to recovering admin room access
Signed-off-by: strawberry <strawberry@puppygock.gay>
This commit is contained in:
parent
b362f0e0fa
commit
2fcedad2b1
1 changed files with 12 additions and 1 deletions
|
@ -13,6 +13,17 @@
|
||||||
> If there are things like Compose file issues or Dockerhub image issues, those
|
> If there are things like Compose file issues or Dockerhub image issues, those
|
||||||
> can still be mentioned as long as they're something we can fix.
|
> can still be mentioned as long as they're something we can fix.
|
||||||
|
|
||||||
|
## conduwuit and Matrix issues
|
||||||
|
|
||||||
|
#### Lost access to admin room
|
||||||
|
|
||||||
|
You can reinvite yourself to the admin room through the following methods:
|
||||||
|
- Use the `--execute "users make_user_admin <username>"` conduwuit binary
|
||||||
|
argument once to invite yourslf to the admin room on startup
|
||||||
|
- Use the conduwuit console/CLI to run the `users make_user_admin` command
|
||||||
|
- Or specify the `emergency_password` config option to allow you to temporarily
|
||||||
|
log into the server account (`@conduit`) from a web client
|
||||||
|
|
||||||
## General potential issues
|
## General potential issues
|
||||||
|
|
||||||
#### Potential DNS issues when using Docker
|
#### Potential DNS issues when using Docker
|
||||||
|
@ -30,7 +41,7 @@ workarounds for this are:
|
||||||
- Don't use Docker's default DNS setup and instead allow the container to use
|
- Don't use Docker's default DNS setup and instead allow the container to use
|
||||||
and communicate with your host's DNS servers (host's `/etc/resolv.conf`)
|
and communicate with your host's DNS servers (host's `/etc/resolv.conf`)
|
||||||
|
|
||||||
## Rocksdb / database issues
|
## RocksDB / database issues
|
||||||
|
|
||||||
#### Direct IO
|
#### Direct IO
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue