diff options
Diffstat (limited to 'docs/content/doc/help')
| -rw-r--r-- | docs/content/doc/help/seek-help.en-us.md | 28 | ||||
| -rw-r--r-- | docs/content/doc/help/troubleshooting.en-us.md | 43 |
2 files changed, 49 insertions, 22 deletions
diff --git a/docs/content/doc/help/seek-help.en-us.md b/docs/content/doc/help/seek-help.en-us.md new file mode 100644 index 0000000000..1e6e2d282b --- /dev/null +++ b/docs/content/doc/help/seek-help.en-us.md @@ -0,0 +1,28 @@ +--- +date: "2017-01-20T15:00:00+08:00" +title: "Support Options" +slug: "seek-help" +weight: 10 +toc: true +draft: false +menu: + sidebar: + parent: "help" + name: "Support Options" + weight: 20 + identifier: "seek-help" +--- + +# Support Options + +- [Discord](https://discord.gg/NsatcWJ) +- [#gitea on Freenode](http://webchat.freenode.net?nick=giteachat....&channels=%23gitea&prompt=1) +- [Matrix](https://matrix.to/#/#gitea-dev:matrix.org) + +## Bugs + +If you found a bug, please create an [issue on Github](https://github.com/go-gitea/gitea/issues). + +## Chinese Support + +Support for the Chinese language is provided at [gocn.io](https://gocn.io/topic/Gitea). diff --git a/docs/content/doc/help/troubleshooting.en-us.md b/docs/content/doc/help/troubleshooting.en-us.md index aa9af456ae..1b2a52ca81 100644 --- a/docs/content/doc/help/troubleshooting.en-us.md +++ b/docs/content/doc/help/troubleshooting.en-us.md @@ -7,7 +7,7 @@ toc: true draft: false menu: sidebar: - parent: "Help" + parent: "help" name: "Troubleshooting" weight: 20 identifier: "troubleshooting" @@ -15,43 +15,41 @@ menu: # Troubleshooting -This page contains some common issues you can run into and their solutions. +This page contains some common seen issues and their solutions. ## SSH issues -If you are having issues with reaching your repositories over `ssh` while the -Gitea web front-end and `https` based git operations work fine, consider -looking at the following items. +For issues reaching repositories over `ssh` while the gitea web front-end, but +`https` based git repository access works fine, consider looking into the following. ``` Permission denied (publickey). fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. ``` -This error signifies that the server rejected your log in attempt, check the +This error signifies that the server rejected a log in attempt, check the following things: * On the client: * Ensure the public and private ssh keys are added to the correct Gitea user. - * Make sure there are no issues in your remote url, ensure the name of the + * Make sure there are no issues in the remote url, ensure the name of the git user (before the `@`) is spelled correctly. - * Ensure the public and private ssh keys are available and reachable on the - client machine. - * Try to `ssh git@myremote.example` to ensure that everything is set up - properly. + * Ensure public and private ssh keys are correct on client machine. + * Try to connect using ssh (ssh git@myremote.example) to ensure a connection + can be made. * On the server: - * Check the permissions of the `.ssh` directory in the home directory of your - `git` user. + * Make sure the repository exists and is correctly named. + * Check the permissions of the `.ssh` directory in the system user's home directory. * Verify that the correct public keys are added to `.ssh/authorized_keys`. Try to run `Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys)` on the Gitea admin panel. + * Read gitea logs. + * Read /var/log/auth (or similar). + * Check permissions of repositories. -If you get a similar error without the public key part (shown below) then -authentication succeeded, but some other setting is preventing ssh from -reaching the correct repository. +The following is an example of a missing public SSH key where authentication +succeeded, but some other setting is preventing SSH from reaching the correct +repository. ``` fatal: Could not read from remote repository. @@ -63,7 +61,8 @@ and the repository exists. In this case, look into the following settings: * On the server: - * Make sure that your `git` user has a usable shell set. You can verify this - with `getent passwd git | cut -d: -f7`, `chsh` can be used to modify this. + * Make sure that the `git` system user has a usable shell set + * Verify this with `getent passwd git | cut -d: -f7` + * `usermod` or `chsh` can be used to modify this. * Ensure that the `gitea serv` command in `.ssh/authorized_keys` uses the - proper configuration file. + correct configuration file. |