docs.coopcloud.tech/docs/abra/trouble.md

34 lines
1.1 KiB
Markdown
Raw Normal View History

2022-01-26 10:47:44 +00:00
---
2022-01-27 09:27:23 +00:00
title: Troubleshoot
2022-01-26 10:47:44 +00:00
---
2022-02-02 20:27:05 +00:00
## Where do I report `abra` bugs / feature requests?
2022-02-03 13:37:34 +00:00
You can use [this issue tracker](https://git.coopcloud.tech/coop-cloud/abra/issues/new).
2022-02-02 20:27:05 +00:00
## I'm having a bad day, where do I find a human?
2022-02-03 13:37:34 +00:00
Please see [the contact page](/intro/contact).
2022-02-02 20:27:05 +00:00
2022-01-27 10:50:40 +00:00
## SSH connection issues?
2022-01-26 10:47:44 +00:00
2022-01-27 10:50:40 +00:00
TODO.
## "abra server ls" shows the wrong details?
2022-02-03 13:37:34 +00:00
You can use `abra server rm` to remove the incorrect details. Make sure to take a backup of your `~/.abra/servers/<domain>` first.
However, if you have Docker installed on the same machine you have `abra`, then there might be some confusion. If you run `docker context ls` you'll see that Docker uses context connection strings also. `abra` simply uses this approach. Sometimes, your Docker defined context details & your `abra` context details can get out of sync. You can use `docker context rm` to resolve this.
If you need to create a new context from Docker, you can do:
```
docker context create <domain> --docker "host=ssh://<user>@<domain>:<port>"
```
(This is what we used to before we wrote `abra` to make it more convenient.)
2022-01-27 10:50:40 +00:00
## Command-line flag handling is weird?
TODO.