Setup:
- migrated repository(ies) from GitHub.com to private (Synology hosted) Gitlab repository(ies)
- created an HTTPs endpoint using Synology "reverse proxy" that maps HTTPs to internal HTTP endpoint
- In Synology, assigned a certificate for this HTTPs endpoint(+ port)
- In client machine, added the public certificate file to the linux trusted certs store(/etc/ssl/certs/)
- In client machine, running the command git clone works
- Still in client machine, running "go get" or "go mod tidy" on a directory with go.mod with this endpoint in the list of "replace" statement fails (after pausing/waiting for few seconds) with the error msg: no secure protocol found for repositoryExample:replace (github.com/abc/md5-simd v1.1.1 => synology.com/abc/md5-simd.git v1.1.1)
What seems to be wrong here? The "git clone " works. Is there a separate trusted certs store for "go get"? If yes, location please?
NOTE: I am using via "reverse proxy" approach as described, but will try turning on the built-in HTTPs feature of Gitlab (soon/next).
But I am wondering why this setup/sln does not work, anybody?
