# \[SOLVED\] Error When Cloning via HTTPS

**URL:** <https://forum.gitea.com/t/solved-error-when-cloning-via-https/147>\
**Category:** Install/Maintain/Configure\
**Created:** [December 20, 2017, 3:55pm UTC](https://forum.gitea.com/t/solved-error-when-cloning-via-https/147 "2017-12-20T15:55:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcosbaesse](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/marcosbaesse/32/4722_2.png) [@marcosbaesse](https://forum.gitea.com/u/marcosbaesse)\
**Post date:** [December 20, 2017, 3:55pm UTC](https://forum.gitea.com/t/solved-error-when-cloning-via-https/147/1 "2017-12-20T15:55:35Z")

</div>

Hi all,

I got an Windows Server on local network that is not available online and its accessed via Hostname.

The server is running Apache with an Self Signed Certificate. We access Gitea over an reverse proxy in Apache from ‘[https://serverhostname/gitea](https://serverhostname/gitea)’ resource to port 3000 (where gitea service is running).

We want to use https on the local network, but when I tried to clone an repository, I got the following error message:

`fatal: unable to access 'https://serverhostname/gitea/marcos.baesse/teste.git/': schannel: next InitializeSecurityContext failed: SEC_E_UNTRUSTED_ROOT (0x80090325) - The certification chain was issued by an entity that is unreliable.`

What should I do to fix this?

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [December 21, 2017, 6:11am UTC](https://forum.gitea.com/t/solved-error-when-cloning-via-https/147/2 "2017-12-21T06:11:03Z")

</div>

This should be a cert problem on your reverse proxy. maybe set `git config --global http.sslVerify false` on every client side to solve the issue.

---

<div class="post-metadata">

**Author:** ![marcosbaesse](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/marcosbaesse/32/4722_2.png) [@marcosbaesse](https://forum.gitea.com/u/marcosbaesse)\
**Post date:** [December 27, 2017, 10:12am UTC](https://forum.gitea.com/t/solved-error-when-cloning-via-https/147/3 "2017-12-27T10:12:04Z")

</div>

Thanks. That helps a lot. I have searched for how to make an self signature trusted, but it seems be not possible as our server is acessible only in the local network, it does not has an public address. But with this, we can focus on have the work done and fix this problem with certificates later.

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [May 11, 2026, 6:02pm UTC](https://forum.gitea.com/t/solved-error-when-cloning-via-https/147/4 "2026-05-11T18:02:44Z")

</div>