Forgejo - Revision history

KN6DWI: Provide possible explanation for permission denied publickey

2026-09-15T23:07:17Z

Provide possible explanation for permission denied publickey

← Older revision		Revision as of 23:07, 15 September 2026
Line 57:		Line 57:
	=== Can't clone repository over SSH ===		=== Can't clone repository over SSH ===
	Forgejo does not operate on the same SSH port as your system's <code>sshd</code> server. The default port for Forgejo SSH is 222. Unless you change this to 22 (and move your <code>sshd</code> port somewhere else), you'll have to specify the correct port when cloning the repository. For example, <code>git clone ssh://git@yoursite.org:<port here>/username/repository</code>.		Forgejo does not operate on the same SSH port as your system's <code>sshd</code> server. The default port for Forgejo SSH is 222. Unless you change this to 22 (and move your <code>sshd</code> port somewhere else), you'll have to specify the correct port when cloning the repository. For example, <code>git clone ssh://git@yoursite.org:<port here>/username/repository</code>.

			If you're getting <code>Permission denied (publickey)</code>, you may be attempting to SSH into the <code>sshd</code> port rather than the Forgejo port.

KN6DWI: Removed extraneous link

2026-09-15T23:05:06Z

Removed extraneous link

← Older revision		Revision as of 23:05, 15 September 2026
Line 7:		Line 7:

	== Step 1: Install Forgejo ==		== Step 1: Install Forgejo ==
	Go to the [https://codeberg.org/forgejo-contrib/delightful-forgejo#packaging delightful forgejo] repository and check whether Forgejo has been packaged for your operating system or distribution. If so, install using your package manager. Otherwise, go to the [https://forgejo.org/docs/latest/admin/installation/ Forgejo installation page]~~(https://forgejo.org/releases/)~~ , decide whether you're going to install from binary or from a docker container, and follow the corresponding instructions. Make sure you complete initial setup before moving to the next step.		Go to the [https://codeberg.org/forgejo-contrib/delightful-forgejo#packaging delightful forgejo] repository and check whether Forgejo has been packaged for your operating system or distribution. If so, install using your package manager. Otherwise, go to the [https://forgejo.org/docs/latest/admin/installation/ Forgejo installation page], decide whether you're going to install from binary or from a docker container, and follow the corresponding instructions. Make sure you complete initial setup before moving to the next step.

	== Step 2: Open Forgejo ports in your device firewall ==		== Step 2: Open Forgejo ports in your device firewall ==

KN6DWI: Wrote instructions for pushing commit to remote

2026-09-15T21:52:04Z

Wrote instructions for pushing commit to remote

← Older revision		Revision as of 21:52, 15 September 2026
Line 40:		Line 40:

	=== Make a commit and push it to the remote repository ===		=== Make a commit and push it to the remote repository ===
	* Make a commit ~~on your local repository~~ and push it to the remote repository		After cloning the repository, make a commit and push it to the remote repository with the following steps:
			# Create or modify a file in the repository's folder
			# Add your changes with <code>git add <file></code>
			# Commit your changes with <code>git commit -m <message></code>
			# Push to the remote repository with <code>git push</code>

	If these are all working, you should be good to go!		The push command should proceed through enumerating objects, counting objects, delta compression, compressing objects, and writing objects, then finish. If it throws an error (any line starting with <code>fatal</code>), then you may have a configuration issue and should consult the troubleshooting section. If these are all working, you should be good to go!

	== Troubleshooting ==		== Troubleshooting ==

KN6DWI: Instruct users on creating a repository

2026-09-15T19:07:57Z

Instruct users on creating a repository

← Older revision		Revision as of 19:07, 15 September 2026
Line 22:		Line 22:
	Make sure your Forgejo instance is working by testing a few operations.		Make sure your Forgejo instance is working by testing a few operations.
	=== Create a repository using the web UI ===		=== Create a repository using the web UI ===
			Log into Forgejo and go to the Forgejo home page. Click the plus button at the top right, and click "New Repository." Fill in the details (specifics don't matter, since this is a test), and if the repository is successfully created, move on to the next step.

			[[File:forgejo_create_repo.png]]

	=== Clone the repository over HTTP ===		=== Clone the repository over HTTP ===

KN6DWI: Split repo cloning into two sections

2026-09-15T18:27:26Z

Split repo cloning into two sections

← Older revision		Revision as of 18:27, 15 September 2026
Line 23:		Line 23:
	=== Create a repository using the web UI ===		=== Create a repository using the web UI ===

	=== Clone the repository ===		=== Clone the repository over HTTP ===
	Copy the HTTP URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. It should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.		Copy the HTTP URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. It should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.

Line 30:		Line 30:
	If the clone completes without error, delete the folder and move on to cloning via SSH. If you get some error such as "Repository not found" or similar, you may have a configuration issue, and should proceed to the troubleshooting section.		If the clone completes without error, delete the folder and move on to cloning via SSH. If you get some error such as "Repository not found" or similar, you may have a configuration issue, and should proceed to the troubleshooting section.

			=== Clone the repository over SSH ===
	Copy the SSH URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. Just like before, it should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.		Copy the SSH URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. Just like before, it should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.
	[[File:forgejo_clone_ssh.png\| A screenshot of the SSH git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]		[[File:forgejo_clone_ssh.png\| A screenshot of the SSH git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]

KN6DWI: Described steps for cloning repository

2026-09-15T18:26:55Z

Described steps for cloning repository

← Older revision		Revision as of 18:26, 15 September 2026
Line 24:		Line 24:

	=== Clone the repository ===		=== Clone the repository ===
	* Clone the ~~repository using~~ HTTP		Copy the HTTP URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. It should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.

	[[File:forgejo_clone_http.png\| A screenshot of the HTTP git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]		[[File:forgejo_clone_http.png\| A screenshot of the HTTP git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]
	* Clone the ~~repository using~~ SSH
			If the clone completes without error, delete the folder and move on to cloning via SSH. If you get some error such as "Repository not found" or similar, you may have a configuration issue, and should proceed to the troubleshooting section.

			Copy the SSH URL from Forgejo, go to your terminal, and run <code>git clone <URL></code>. Just like before, it should go through "Enumerating objects," "Counting objects," and "Compressing objects" before finishing.
	[[File:forgejo_clone_ssh.png\| A screenshot of the SSH git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]		[[File:forgejo_clone_ssh.png\| A screenshot of the SSH git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]

			If the clone completes without error, delete the folder and move on to cloning via SSH. If you get some error such as "Repository not found" or "Permission denied: pubkey," you may have a configuration issue, and should proceed to the troubleshooting section.

	=== Make a commit and push it to the remote repository ===		=== Make a commit and push it to the remote repository ===

KN6DWI: Insert repo clone URL screenshots

2026-09-14T23:24:23Z

Insert repo clone URL screenshots

← Older revision		Revision as of 23:24, 14 September 2026
Line 25:		Line 25:
	=== Clone the repository ===		=== Clone the repository ===
	* Clone the repository using HTTP		* Clone the repository using HTTP
			[[File:forgejo_clone_http.png\| A screenshot of the HTTP git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]
	* Clone the repository using SSH		* Clone the repository using SSH
			[[File:forgejo_clone_ssh.png\| A screenshot of the SSH git clone URL on a forgejo repository. The repository being cloned is KN6DWI/torment-nexus.git.]]

	=== Make a commit and push it to the remote repository ===		=== Make a commit and push it to the remote repository ===

KN6DWI: Created sections

2026-09-14T23:13:27Z

Created sections

← Older revision		Revision as of 23:13, 14 September 2026
Line 20:		Line 20:

	== Step 4: Validate Forgejo functionality ==		== Step 4: Validate Forgejo functionality ==
	Make sure your Forgejo instance is working by testing a few operations:		Make sure your Forgejo instance is working by testing a few operations.
	* Create a repository using the web UI		=== Create a repository using the web UI ===

			=== Clone the repository ===
	* Clone the repository using HTTP		* Clone the repository using HTTP
	* Clone the repository using SSH		* Clone the repository using SSH

			=== Make a commit and push it to the remote repository ===
	* Make a commit on your local repository and push it to the remote repository		* Make a commit on your local repository and push it to the remote repository

KN6DWI: Wrote troubleshooting instructions

2026-09-14T22:47:50Z

Wrote troubleshooting instructions

← Older revision		Revision as of 22:47, 14 September 2026
Line 29:		Line 29:

	== Troubleshooting ==		== Troubleshooting ==
			=== Can't connect to Forgejo web UI ===
			* Make sure you're accessing the correct port. Unless you specify the port, your browser will default to port 80 for HTTP or port 443 for HTTPS. The default port for the web UI is 3000.
			* Use <code>systemctl status <name of unit></code> to make sure your 44Net Connect tunnel is up. The name of the tunnel's <code>systemd</code> unit should be <code>wg-quick@<name of config file></code>.
			* If you're using Docker, make sure your port mappings are correct. Those can be viewed by running <code>sudo docker ps -a</code> to list all containers. Containers created using Docker compose can have their port mappings viewed in their compose file.
			* If you're not using Docker, ensure your device firewall has the correct ports open. <code>firewall-cmd</code> users should also make sure their 44Net Connect WireGuard interface is in the correct zone.

			=== Can't clone repository over SSH ===
			Forgejo does not operate on the same SSH port as your system's <code>sshd</code> server. The default port for Forgejo SSH is 222. Unless you change this to 22 (and move your <code>sshd</code> port somewhere else), you'll have to specify the correct port when cloning the repository. For example, <code>git clone ssh://git@yoursite.org:<port here>/username/repository</code>.

KN6DWI: Instruct user on test operations

2026-09-14T22:30:53Z

Instruct user on test operations

← Older revision		Revision as of 22:30, 14 September 2026
Line 20:		Line 20:

	== Step 4: Validate Forgejo functionality ==		== Step 4: Validate Forgejo functionality ==
			Make sure your Forgejo instance is working by testing a few operations:
			* Create a repository using the web UI
			* Clone the repository using HTTP
			* Clone the repository using SSH
			* Make a commit on your local repository and push it to the remote repository

			If these are all working, you should be good to go!

	== Troubleshooting ==		== Troubleshooting ==