From f2aa6ef64c5e77bbefbd3d64b2669112962b25c2 Mon Sep 17 00:00:00 2001
From: AJ ONeal <aj@daplie.com>
Date: Wed, 25 Oct 2017 17:27:59 -0600
Subject: [PATCH] other issues encountered

---
 README.md | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

diff --git a/README.md b/README.md
index b3d3ea6..d734d97 100644
--- a/README.md
+++ b/README.md
@@ -30,3 +30,42 @@ sudo systemctl restart gitea
 ## Error 226/Namespace
 
 Most likely a directory that is supposed to be writable doesn't exist.
+
+## Failed to get repository owner (foobar): no such table: user
+
+Your `custom/conf/app.ini` has a line like this:
+
+```
+[database]
+DB_TYPE = sqlite3
+PATH = data/gogs.db
+```
+
+And it should probably look like this instead:
+
+```
+[database]
+DB_TYPE = sqlite3
+PATH = /opt/gitea/data/gitea.db
+```
+
+## Gitea: Invalid key ID
+
+```
+Gitea: Invalid key ID
+Invalid key ID[key-2]: public key does not exist [id: 2]
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights
+```
+
+You are connecting to gitea with a different ssh key (usually `id_rsa.pub`)
+than the one you uploaded. You can usually fix this by uploading your default key
+or by manually specifying which key to use, for example:
+
+`~/.ssh/config`:
+```
+Host git.example.com
+  User gitea
+  IdentityFile ~/.ssh/id_rsa
+```