Debian 9.9 w/Gitea 1.8.3 running as user git and Nginx 1.10.3
Installation, for the most part, was straight-forward and without incident as per:
Gitea is listening on TCP port 666 and Gitea’s SSH server is listening on TCP port 22 with the following lines in gitea.service uncommented in order to achieve this:
Site Administration ==> Configuration:
I’m unable to affect any changes in this section, specifically, any of the checkboxes. app.ini was chmod’d 644 with ownership git:git
I thought that maybe if I changed it to 646 or 666 it would be, then restarted the service, but still, I’m unable to make any changes unless I edit app.ini directly in a shell.
I initially noticed this because I was unable to connect or affect a clone via:
$ git clone -vv firstname.lastname@example.org:username/testrepo_1.git
So I added checked the cheat sheet at https://docs.gitea.io/en-us/config-cheat-sheet/ which indicated that, by default, Gitea’s SSH server is disabled from starting up (Not what the install script at the website indicated when installing Gitea and asked if I wanted it):
From the Config Cheat Sheet page at Github:
This line wasn’t even in app.ini, so I added it, setting it thus:
[server] LOCAL_ROOT_URL = http://localhost:666/ START_SSH_SERVER = true SSH_DOMAIN = localhost DOMAIN = localhost HTTP_PORT = 666 ROOT_URL = http://hostname.sld.tld/ DISABLE_SSH = false SSH_PORT = 22
Everything else was already there. I also have questions about LOCAL_ROOT_URL, SSH_DOMAIN, and DOMAIN, as they are set to localhost. Shouldn’t they be reflect otherwise? Especially the latter two, with a value of 0.0.0.0 or something else besides just localhost?
after stopping and starting Gitea, I saw port 22 showing up in netstat and was able to connect via ssh and effect a clone and a push back to the repo.
Why did Gitea behave in this way?
Did I do something wrong during installation?
Why can’t I still affect any changes via the GUI?
Any thoughts, suggestions, are appreciated.