luckyimnotanigger/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2025-05-31 11:52:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

General documentation cleanup (#3317)

Browse source 
* Clean up spelling, grammar, perspective, whitespace, language, markup, etc.
This commit is contained in:
Michael Lustfield 2018-01-08 16:48:42 -06:00 • committed by Kim "BKC" Carlbäcker
parent 923c0105f4
commit 3ee8be3849
30 changed files with 500 additions and 279 deletions
Download patch file Download diff file Expand all files Collapse all files

43
docs/content/doc/help/troubleshooting.en-us.md
View file

@ -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.