Cannot run scripts from site in ipv6 only setup #633

Closed
opened 2026-02-04 20:27:50 +03:00 by OVERLORD · 12 comments
Owner

Originally created by @vesnikos on GitHub (Mar 14, 2025).

Please verify that you have read and understood the guidelines.

yes

What type of issue is this?

No response

A clear and concise description of the issue.

Because there's no ipv6 address for www.github.com (it's 2025 and still working on it)

> nslookup -type=AAAA github.com 1.1.1.1
Server: one.one.one
Adress: 1.1.1.1

a workaround would be to use the raw.githubusercontent.com domain whch has. Also the internals scripts use the raw.githubusercontent.com.

Which browser are you using?

Chrome

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @vesnikos on GitHub (Mar 14, 2025). ### Please verify that you have read and understood the guidelines. yes ### What type of issue is this? _No response_ ### A clear and concise description of the issue. Because there's no ipv6 address for www.github.com (it's 2025 and still working on it) ```bash > nslookup -type=AAAA github.com 1.1.1.1 Server: one.one.one Adress: 1.1.1.1 ``` a workaround would be to use the `raw.githubusercontent.com` domain whch has. Also the internals scripts use the `raw.githubusercontent.com`. ### Which browser are you using? Chrome ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the website label 2026-02-04 20:27:50 +03:00
Author
Owner

@MickLesk commented on GitHub (Mar 14, 2025):

What are excactly your Issue? Where? Which Part? Which Call? You do an Frontend-Issue.

@MickLesk commented on GitHub (Mar 14, 2025): What are excactly your Issue? Where? Which Part? Which Call? You do an Frontend-Issue.
Author
Owner

@vesnikos commented on GitHub (Mar 14, 2025):

When I copy/paste a script e.g. :

Image

in the console of a box configured only to use ipv6

Image

it silently fails

Image

The root reason is that github.com cannot resolve to an ipv6 because there's no AAAA in any DNS. this is an issue of github.com as have not provided one of their domain. this can be verified at https://api.github.com/meta

As a workaround I need to manually edit the scripts domain to use https://raw.githubusercontent.com...

Image

@vesnikos commented on GitHub (Mar 14, 2025): When I copy/paste a script e.g. : ![Image](https://github.com/user-attachments/assets/b92679c1-d5c8-43ab-9770-fca39fe8fdc9) in the console of a box configured only to use ipv6 ![Image](https://github.com/user-attachments/assets/f7cc7741-3c90-4513-bab6-9c65df8de937) it silently fails ![Image](https://github.com/user-attachments/assets/5b38095e-c36b-47f7-867f-50843bf0d04b) The root reason is that github.com cannot resolve to an ipv6 because there's no AAAA in any DNS. this is an issue of github.com as have not provided one of their domain. this can be verified at https://api.github.com/meta As a workaround I need to manually edit the scripts domain to use `https://raw.githubusercontent.com...` ![Image](https://github.com/user-attachments/assets/b69bdc4b-5339-4190-a7c1-54b8709d9b5f)
Author
Owner

@vesnikos commented on GitHub (Mar 14, 2025):

If i misslabel'ed it, happy for someone who can to re-label it

@vesnikos commented on GitHub (Mar 14, 2025): If i misslabel'ed it, happy for someone who can to re-label it
Author
Owner

@MickLesk commented on GitHub (Mar 14, 2025):

hm i doesnt use only ipv6, its hard to fix this.

Does work the wget call? (without bash).
Idk where i can fix this, because i cant change the wget for all. The effects are uncertain, as there is sometimes much more to it than a simple call.

@MickLesk commented on GitHub (Mar 14, 2025): hm i doesnt use only ipv6, its hard to fix this. Does work the wget call? (without bash). Idk where i can fix this, because i cant change the wget for all. The effects are uncertain, as there is sometimes much more to it than a simple call.
Author
Owner

@tremor021 commented on GitHub (Mar 14, 2025):

i've said it privately, gonna repeat it here. having only ipv6 networking is really going to hurt you @vesnikos since not even the biggest players on the global internet space addopted it.

you can have both ipv4 and ipv6 addresses assigned on your network. when github turns on ipv6, just disable ipv4

@tremor021 commented on GitHub (Mar 14, 2025): i've said it privately, gonna repeat it here. having only ipv6 networking is really going to hurt you @vesnikos since not even the biggest players on the global internet space addopted it. you can have both ipv4 and ipv6 addresses assigned on your network. when github turns on ipv6, just disable ipv4
Author
Owner

@vesnikos commented on GitHub (Mar 14, 2025):

hm i doesnt use only ipv6, its hard to fix this.

Does work the wget call? (without bash). Idk where i can fix this, because i cant change the wget for all. The effects are uncertain, as there is sometimes much more to it than a simple call.

wget is very happy to work with ipv6 even without the -6 flag

The only real universal solution I see here is replace the pointer the website for the scripts from github to githubusercontent

ie from:

bash -c "$(wget -qLO - *https://github.com*/community-scripts/ProxmoxVE/raw/main/misc/post-pve-install.sh)"

to

bash -c "$(wget -qLO - *https://raw.githubusercontent.com*/community-scripts/ProxmoxVE/main/misc/post-pve-install.sh)"`
@vesnikos commented on GitHub (Mar 14, 2025): > hm i doesnt use only ipv6, its hard to fix this. > > Does work the wget call? (without bash). Idk where i can fix this, because i cant change the wget for all. The effects are uncertain, as there is sometimes much more to it than a simple call. `wget` is very __happy__ to work with ipv6 even without the -6 flag The only real universal solution I see here is replace the pointer the website for the scripts from **github** to **githubusercontent** ie from: ~~~bash bash -c "$(wget -qLO - *https://github.com*/community-scripts/ProxmoxVE/raw/main/misc/post-pve-install.sh)" ~~~ to ~~~bash bash -c "$(wget -qLO - *https://raw.githubusercontent.com*/community-scripts/ProxmoxVE/main/misc/post-pve-install.sh)"` ~~~
Author
Owner

@vesnikos commented on GitHub (Mar 14, 2025):

i've said it privately, gonna repeat it here. having only ipv6 networking is really going to hurt you @vesnikos since not even the biggest players on the global internet space addopted it.

you can have both ipv4 and ipv6 addresses assigned on your network. when github turns on ipv6, just disable ipv4

This is a bit off-topic with the nature of the ticket; i'd love to read your opinions on either if IETF gone wrong or if cisco has dropped the ball somewhere with their ipv6 impelementation in within IOS XE or there is a lack of training from network engineers, in a blog or something if you have

@vesnikos commented on GitHub (Mar 14, 2025): > i've said it privately, gonna repeat it here. having only ipv6 networking is really going to hurt you [@vesnikos](https://github.com/vesnikos) since not even the biggest players on the global internet space addopted it. > > you can have both ipv4 and ipv6 addresses assigned on your network. when github turns on ipv6, just disable ipv4 This is a bit off-topic with the nature of the ticket; i'd love to read your opinions on either if IETF gone wrong or if cisco has dropped the ball somewhere with their ipv6 impelementation in within IOS XE or there is a lack of training from network engineers, in a blog or something if you have
Author
Owner

@MickLesk commented on GitHub (Mar 19, 2025):

GitHub.com still doesn’t support IPv6 (no AAAA records), which makes things tricky for IPv6-only users. While raw.githubusercontent.com works with IPv6, we won’t automate the switch because it could cause unexpected issues in different environments.

Instead of checking IPv6 and changing URLs dynamically, we’re leaving this as a manual adjustment. If you're on an IPv6-only network, you’ll need to swap github.com with raw.githubusercontent.com yourself.

Hopefully, GitHub enables IPv6 at some point, but until then, this is something that has to be handled manually.

We might reconsider this in a future refactor of the website, but that would mean evaluating client-side network data (IPv6-only detection), which we prefer not to do. Also, many existing scripts are built around github.com, so changing this would be a major structural shift.

@MickLesk commented on GitHub (Mar 19, 2025): GitHub.com still doesn’t support **IPv6** (no AAAA records), which makes things tricky for IPv6-only users. While raw.githubusercontent.com works with IPv6, we won’t automate the switch because it could cause unexpected issues in different environments. Instead of checking IPv6 and changing URLs dynamically, we’re leaving this as a manual adjustment. If you're on an IPv6-only network, you’ll need to swap github.com with raw.githubusercontent.com yourself. Hopefully, GitHub enables IPv6 at some point, but until then, this is something that has to be handled manually. We might reconsider this in a future refactor of the website, but that would mean evaluating client-side network data (IPv6-only detection), which we prefer not to do. Also, many existing scripts are built around github.com, so changing this would be a major structural shift.
Author
Owner

@vesnikos commented on GitHub (Mar 19, 2025):

The explanation sounds good to me! Doing the change manually is easier in that context. If there's a place in the website, it would be nice if you had a pointer to this ticket, as it also describes the workaround steps.

@vesnikos commented on GitHub (Mar 19, 2025): The explanation sounds good to me! Doing the change manually is easier in that context. If there's a place in the website, it would be nice if you had a pointer to this ticket, as it also describes the workaround steps.
Author
Owner

@MickLesk commented on GitHub (Mar 19, 2025):

We currently have a roadmap (currently only in Discord) for topics such as rework, etc. It is entered there as a note

@MickLesk commented on GitHub (Mar 19, 2025): We currently have a roadmap (currently only in Discord) for topics such as rework, etc. It is entered there as a note
Author
Owner

@MickLesk commented on GitHub (Apr 2, 2025):

You can try It. Ive merged today an big pr with curls and frontend things

@MickLesk commented on GitHub (Apr 2, 2025): You can try It. Ive merged today an big pr with curls and frontend things
Author
Owner

@vesnikos commented on GitHub (Apr 2, 2025):

thanks. it seems to work. Noticed a warning when tried to install iventoy

curl: (7) Failed to connect to api.community-scripts.org port 80 after 1 ms: Couldn't connect to server

I did a
nslookup -type=AAAA api.community-scripts.org
which came back nothing

But other than that it works

@vesnikos commented on GitHub (Apr 2, 2025): thanks. it seems to work. Noticed a warning when tried to install [iventoy](https://community-scripts.github.io/ProxmoxVE/scripts?id=iventoy) ~~~bash curl: (7) Failed to connect to api.community-scripts.org port 80 after 1 ms: Couldn't connect to server ~~~ I did a nslookup -type=AAAA api.community-scripts.org which came back nothing But other than that it works
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#633