Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ajscam

Members
  • Joined

  • Last visited

  1. In case anyone finds their way here: Change the Repository to gitea/gitea:latest-rootless
  2. Port 22 is already in use by my Unraid server, so to deploy Gitea when port 22 is already in use, I must configure Gitea to use a different SSH port (e.g., 2222) and ensure the built-in SSH server is enabled using container Variable: GITEA__server__START_SSH_SERVERT=TRUE. When I do this, the container won't start becuase: 2026/02/28 14:17:46 modules/ssh/ssh_graceful.go:25:listen() [F] Failed to start SSH server: listen tcp :22: bind: address already in use So I added 'GITEA__server__DISABLE_SSH'='TRUE'. Now the container starts. I need to keep unraid listening on port 22. I thought -p '2222:22/tcp' would map unraid port 2222 -> gitea port 22 Should I set the gitea container to Host networking to work around this issue?
  3. Has anyone been able to get this running? I had to add GITEA__server__DISABLE_SSH=TRUE otherwise the container wouldn't start: 2026/02/28 14:17:46 modules/ssh/init.go:27:Init() [I] SSH server started on ":22". Ciphers: default, key exchange algorithms: default, MACs: default 2026/02/28 14:17:46 modules/graceful/server.go:50:NewServer() [I] Starting new SSH server: tcp::22 on PID: 17 2026/02/28 14:17:46 .../indexer/issues/indexer.go:155:InitIssueIndexer.2() [I] Issue Indexer Initialization took 3.019065ms 2026/02/28 14:17:46 modules/graceful/server.go:76:(*Server).ListenAndServe() [E] Unable to GetListener: listen tcp :22: bind: address already in use 2026/02/28 14:17:46 modules/ssh/ssh_graceful.go:25:listen() [F] Failed to start SSH server: listen tcp :22: bind: address already in use Received signal 15; terminating. However, I still can't connect to the web interface on :3000. From the console, I see this: / # ps -ef | grep git 15 root 0:00 s6-supervise gitea 17 git 0:01 /usr/local/bin/gitea web 132 root 0:00 grep git / # netstat -nap | grep LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 18/sshd -D -e [list tcp 0 0 :::22 :::* LISTEN 18/sshd -D -e [list tcp 0 0 :::3002 :::* LISTEN - This is the docker run: docker run -d --name='Gitea' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="nas" -e HOST_CONTAINERNAME="Gitea" -e 'GITEA__server__START_SSH_SERVER'='TRUE' -e 'GITEA__server__DISABLE_SSH'='TRUE' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/fanningert/unraid-docker-templates/master/fanningert/icons/gitea.png' -p '2222:22/tcp' -p '3002:3000/tcp' -v '/mnt/user/appdata/gitea':'/data':'rw' 'gitea/gitea'

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.