Generic

In case anyone had the same issue as above, I have no idea what was actually wrong but after spending hours mucking around trying different things what I believe fixed it was using `git clone http://....` rather than `git clone https://...`. This bought up the git credential manager instead of opening a browser page of my server login, and upon putting my user/password into the manager (it should have already had both and in fact had the user name auto-filled so beats me) it all worked. Now it is back to all working with using `git clone https://...` as it was previously and in fact git will give me an output saying it is changing over to https if I use http. Again, I have no idea why this happened or what was going on but it seems to be working and I'm not going to worry about it any more then that.

Hi All, I've had Gitea running for quite a while and it's all been working great. However, that was with all the repos set to public, I've now changed it so that some repos are private and am now struggling to access them through Git CLI. It still works perfectly through the browser and I can pull public repos with no issues. When I try and clone a private repo using HTTPS it first opens a login page on my Gitea instance and then when I log in it redirects to an error page, with firefox saying: Secure Connection Failed An error occurred during a connection to 127.0.0.1:58683. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG This is consistent on other browsers and I haven't been able to figure out why it is happening. Looking through the socker logs as I request the repo shows: 024/03/07 17:26:35 ...eb/routing/logger.go:102:func1() router: completed GET {REPO}.git/info/refs?service=git-upload-pack for 172.19.0.2:46594, 401 Unauthorized in 4.4ms @ repo/githttp.go:532(repo.GetInfoRefs) 2024/03/07 17:26:40 ...eb/routing/logger.go:102:func1() router: completed GET /login/oauth/authorize?response_type=code&client_id={VALUE}&state={VALUE}&code_challenge_method=S256&code_challenge=k_{VALUE}&redirect_uri=http%3a%2f%2f127.0.0.1%3a50480%2f for 172.19.0.2:46618, 303 See Other in 14.8ms @ auth/oauth.go:362(auth.AuthorizeOAuth) Which doesn't seem to show an obvious problems? Again, I can access everything perfectly normally through the browser it's just trying to pull it over Git CLI. As a bonus question, does anyone have a guide for setting up SSH? I can't figure out how that works either. I have a SSH key (called "id_ed25519") in ~/.ssh which I have registered with the SSH agent as described [here](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent) as well as adding and verifying the key on my GItea account through the browser. When I then try and clone a repo using the address given on the browser, `git clone ssh://git@gitea.{MY_DOMAIN}:24/{REPO}.git`, then it just times out and says the host is unreachable. I realise SSH is typically port 22 but that is already used and so the container won't start if it tries to use that port so it is changed to "Git over SSH container port 22, host port 24". and shows up as SWAG connecting the host port 24 to the container port 22. SSH is enabled in the app.ini file for Gitea. I can post any more configuration files if required but am honestly not sure what is pertinent. Thanks in advance.

Hi, I'm running 6.12.6 and last night tried to change out my cache drive. I changed all the shares to have mover take them into the data pool and then used the mover to transfer everything over. As far as I could tell everything was off the cache. I then replaced the cache pool drive and got it formatted and running. Now I've changed the share properties to have things go back onto the cache and run the mover a few times (Docker is disabled) before restarting docker and installing my old applications using the Apps->Previous Apps thing. Essentially, everything is broken. The docker containers have been loaded correctly with their templates and have the same setup as previously but none of them work properly and some are completely un-accessible. At one point I was able to access the Nextcloud UI through the local network but it was at the setup screen asking me do the whole setup procedure again, i.e. admin account and link to a database, but now it just has a page saying internal server error. Additionally, Mariadb had the correct login details in the shell but on logging in as root it showed no users on mysql.user apart from root, which there definitely should be. I have also tried moving the System share containing /docker/docker.img (again with docker disabled) by setting mover as Array->Cache and invoking the mover and it showed as working but it doesn't seem to have made any difference. At this point it doesn't seem like there has been any loss of data from anywhere which I guess is a relief but I've spent hours smashing my head against a wall and getting frustrated with it without being able to make it any better. Any advice would be welcomed, the diagnostics file is attached. A secondary concern is that now the appdata and system shares are unprotected as they are only (?) in the cache pool but I think that is solved by the a backup I can setup? thomasserver-diagnostics-20231211-1312.zip

Legend, done the above and it's all working for me.

Hi everyone, I've got gitea set up and running through the web UI internally but am having some trouble getting it to be accessible through a web url, I am just getting 502 errors. I have it set up using port 24 for SSH as 22 was taken by something else and have got it working with a mysql database through MariaDB. It has a https certificate from swag and that all seems to be fine, I have also added a CNAME record through cloudflare for the subdomain. I have edited the appdata/gitea/gitea/conf/app.ini file to have [server] DOMAIN = gitea.myserver.com SSH_DOMAIN = gitea.myserver.com HTTP_PORT = 3000 ROOT_URL = https://gitea.myserver.com DISABLE_SSH = false SSH_PORT = 24 SSH_LISTEN_PORT = 24 and have saved a copy of /swag/nginx/proxy-confs/gitea.subdomain.conf.sample as gitea.subdomain.conf I have changed round the SSH_PORT and SSH_LISTEN_PORT in the app.ini file to variations of 22 and 24 as I am not sure which it should be and where, advice on this would be appreciated. Gitea is running on a custom network with the ssh port mappings: 172.18.0.5:22/TCP <-> 192.168.1.41:24 Nextcloud and collabora are also on the custom network and are working perfectly on their subdomains. There are no errors in the swag or gitea log files.