Gitea and Forgejo: self-hosted Git (clone over HTTPS)

Gitea and Forgejo are self-hosted Git servers — your own private GitHub, with repositories, issues, pull requests and a wiki. They set up the same way, and there is one platform-specific point that catches people: you clone and push over HTTPS, not SSH.

Finish the install and create your admin

On first visit you may see a short install page. The database is already configured for you, so leave those fields as they are and scroll to the bottom to create the administrator account.

Do this before you share the address. Until the installer is finished, whoever opens the page first gets to create that admin account.

Cloning and pushing: use HTTPS, not SSH

Git's usual git@… SSH remotes need a raw SSH port, which this platform does not expose, so SSH is turned off. Everything works over HTTPS instead — you just use the https:// clone URL the web interface shows you, not the SSH one.

git clone https://YOUR-APP.h1.cnpods.com/yourname/yourrepo.git

When Git asks for a password, do not use your account password directly. Create an access token and use that:

1. In Gitea/Forgejo: Settings → Applications → Generate New Token.
2. Give it a name, select the scopes you need (repository read/write), and generate it.
3. Copy the token — it is shown once.
4. Use your username and paste the token as the password when Git prompts, or bake it into the remote URL.

Your Git client can remember it after the first push, so you only paste it once.

Good to know

• Sign in to the web interface at /user/login with the admin account you created.
• Give the very first boot a minute; it initialises its database before it answers.
• To send notification email (issue mentions, password resets), set your mail settings under the site administration area — see Sending email from your app for how our built-in mail works.