The container Gitea is running in does have a user “git.” You can log into a shell in the running container using portainer, look in the /etc/passwd file and see the git “user” defined. But you should not need to worry about that at all and tampering with it will lead to no good.
You might try disabling SSL to see if that is your problem. Do this on your local system:
git config --global http.sslVerify false
Try accessing a repo. If it works you at least know that SSL is the source of the problem. Do make sure to re enable SSL:
git config --global http.sslVerify true
You can see how your local git is configured for SSL with:
git config --global http.sslBackend
The output could be empty or “openssl”, “schannel” (or maybe “gnutils”). From here you can try a few things.
If your sslbackend in one of the above, try the other. e.g. if it is “openssl” try:
git config --global http.sslBackend schannel
You can try unsetting the backend:
git config --global --unset http.sslBackend
If none of that works, be sure to return sslBackend to the original setting.
I’m traveling so can’t view my local server but maybe some of that will work.