Full disclosure: I am mostly stumbling my way through setting up GitLab and have an admittedly limited knowledge of SSL certificates and that kind of thing.

GitLab is mostly up and running on my server, I am able to visit the web interface and create users and projects without any issues. I run into problems when I attempt to clone or push commits to a repo using HTTPS. The error I get in Git Bash after running the commands that GitLab provides for a new repo is:

fatal: unable to access 'https://my.url/user/repo.git/': SSL certificate problem: self signed certificate

I have set GitLab up using the manual installation method so that I can integrate it with MySQL and Apache2, since I am running a LAMP Ubuntu installation on my server. The goal was to continue to host my normal website on HTTP and run GitLab through HTTPS.

I am not putting code in arepo that requires high security so self signed certs are fine by me for the time being, unless setting up a CA is actually easy. So far everything I have read on setting up a CA doesn't seem like it is easy.

I would just like to be able to points friends to my HTTPS URL so they can create an account and, once granted access to a repo, start pushing commits. It would be nice if it were as easy as it was with my SSH telnet setup for the server, as in PuTTY will warn that the cert isn't trusted but will still allow you to continue. Users should not have to generate their own certs to add to my server.

How can I allow a user created in the web front end of GitLab to push commits to repos they have been granted access to?

解决方法：

git config --global http.sslVerify false


which turns off that check, get a real certificate (free at startssl.com) or use ssh to push.