Originally created by @dansharpy on GitHub (Jan 19, 2025).
I'm trying to set up a git repo using a locally hosted Gitlab as the target. I can clone this on the host using the token I've provided to Komodo, however if I exec into the container it fails with the error fatal: unable to access 'https://gitlab.my.domain/sharpy/misc-repo.git/': Failed to connect to gitlab.my.domain port 443: Connection refused I used the exact command Komodo is using to clone it on the host, but adding the token value.
I've also tried this on a public repo with the same error.
For context I'm using Traefik as reverse proxy, Gitlab and Komodo are on the same host and same (proxy) network. I'm using PiHole to locally resolve DNS addresses, same set up as everything else I host. I've checked logs of Traefik, Komodo and Pihole and can't find the issue.
This is bound to be a DNS error but I can't figure it out! Any pointers?
Originally created by @dansharpy on GitHub (Jan 19, 2025).
I'm trying to set up a git repo using a locally hosted Gitlab as the target. I can clone this on the host using the token I've provided to Komodo, however if I exec into the container it fails with the error `fatal: unable to access 'https://gitlab.my.domain/sharpy/misc-repo.git/': Failed to connect to gitlab.my.domain port 443: Connection refused` I used the exact command Komodo is using to clone it on the host, but adding the token value.
I've also tried this on a public repo with the same error.
For context I'm using Traefik as reverse proxy, Gitlab and Komodo are on the same host and same (proxy) network. I'm using PiHole to locally resolve DNS addresses, same set up as everything else I host. I've checked logs of Traefik, Komodo and Pihole and can't find the issue.
This is bound to be a DNS error but I can't figure it out! Any pointers?
I'm not sure, I'm using Gitea / caddy / coreDns. The dns entries point to the same host for Komodo and Gitea underneath. And it can connect this way. My stack is different obviously but the components should serve the same purposes.
Since it say connection refused, maybe some firewall like thing is stopping it?
@mbecker20 commented on GitHub (Apr 28, 2025):
I'm not sure, I'm using Gitea / caddy / coreDns. The dns entries point to the same host for Komodo and Gitea underneath. And it can connect this way. My stack is different obviously but the components should serve the same purposes.
Since it say connection refused, maybe some firewall like thing is stopping it?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dansharpy on GitHub (Jan 19, 2025).
I'm trying to set up a git repo using a locally hosted Gitlab as the target. I can clone this on the host using the token I've provided to Komodo, however if I exec into the container it fails with the error
fatal: unable to access 'https://gitlab.my.domain/sharpy/misc-repo.git/': Failed to connect to gitlab.my.domain port 443: Connection refusedI used the exact command Komodo is using to clone it on the host, but adding the token value.I've also tried this on a public repo with the same error.
For context I'm using Traefik as reverse proxy, Gitlab and Komodo are on the same host and same (proxy) network. I'm using PiHole to locally resolve DNS addresses, same set up as everything else I host. I've checked logs of Traefik, Komodo and Pihole and can't find the issue.
This is bound to be a DNS error but I can't figure it out! Any pointers?
@nipuna-perera commented on GitHub (Apr 20, 2025):
Did you figure it out? I'm running into the same.
@mbecker20 commented on GitHub (Apr 28, 2025):
I'm not sure, I'm using Gitea / caddy / coreDns. The dns entries point to the same host for Komodo and Gitea underneath. And it can connect this way. My stack is different obviously but the components should serve the same purposes.
Since it say connection refused, maybe some firewall like thing is stopping it?