# IPv6 Git clone fails in discourse-setup, but works on the machine?!?

**URL:** <https://meta.discourse.org/t/ipv6-git-clone-fails-in-discourse-setup-but-works-on-the-machine/280580>\
**Category:** Self-hosting\
**Tags:** dev-install\
**Created:** [September 30, 2023, 2:35am UTC](https://meta.discourse.org/t/ipv6-git-clone-fails-in-discourse-setup-but-works-on-the-machine/280580 "2023-09-30T02:35:06Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![nottoobright](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@nottoobright](https://meta.discourse.org/u/nottoobright)\
**Post date:** [September 30, 2023, 2:35am UTC](https://meta.discourse.org/t/ipv6-git-clone-fails-in-discourse-setup-but-works-on-the-machine/280580/1 "2023-09-30T02:35:07Z")

</div>

My discourse-setup is failing on a Ubuntu 22.04 VPS with the following error:

fatal: unable to access [https://github.com/discourse/discourse.git/:](https://github.com/discourse/discourse.git/:) Could not resolve host: [github.com](http://github.com)

My VPS has only an IPv6 address, but I’m using Dan Win’s github IPv6 proxy: I can ping [github.com](http://github.com), I successfully cloned discourse\_docker.git, and I can clone the exact same discourse.git from the command line on the same VPS. But when the same command is executed by discourse-setup, it cannot resolve [github.com](http://github.com) and fails.

A previous post recommended setting mtu=1400 in my docker.service file, which I did, but it didn’t change anything.

I first assumed this was an IPv6 problem, but the fact that my VPS can access github and clone the package has me confused… I don’t know what the setup is doing differently. I wish there were some way to tell discourse-setup that github.git is already on the server or just to use the server’s default settings that worked.

---

_[View the full topic](https://meta.discourse.org/t/ipv6-git-clone-fails-in-discourse-setup-but-works-on-the-machine/280580)._