phpmyadmin.net is not accessible via IPv6

[miyurusankalpa]

Cannot download phpmyadmin on a IPv6 only server.

both www.phpmyadmin.net and files.phpmyadmin.net does not have AAAA records.

Connecting to files.phpmyadmin.net (files.phpmyadmin.net)|185.93.2.15|:443... failed: Connection timed out.
Connecting to www.phpmyadmin.net (www.phpmyadmin.net)|195.181.174.2|:443... failed: Connection timed out.

phpmyadmin.net does have a AAAA record but, connections are refused.

Connecting to phpmyadmin.net (phpmyadmin.net)|2a01:4f8:13b:15a3::2|:443... failed: Connection refused.

Describe the solution you'd like

1. Fix the connection issue (probably only binded to IPv4 or firewall block) and add AAAA to www subdomain as well.

2. Since files.phpmyadmin.net uses CDN77 as the CDN, I have contacted them asking about IPv6 connectivity. I will update this post once they reply. Got a reply, they dont support IPv6 yet.

[gratuxri]

Just a workaround to download phpmyadmin from debian cdn: http://cdn-fastly.deb.debian.org/debian/pool/main/p/phpmyadmin/phpmyadmin_4.9.5+dfsg1.orig.tar.xz
or just git clone https://salsa.debian.org/phpmyadmin-team/phpmyadmin.git

[williamdes]

This is very clever!
I would add that we have a upstream clean branch that can be used https://salsa.debian.org/phpmyadmin-team/phpmyadmin/-/tree/upstream

Or the temporary upstream-5.x branch

[ibennetch]

Basically since our CDN doesn't support IPv6 (and there are many sites out there that don't), I don't particularly see what should be done about this. I've been waiting for the worldwide move to IPv6 for quite a while now and I just don't see much adoption or need for it with our infrastructure at the moment.

I suppose we could create the AAAA records for www.phpmyadmin.net to point directly at our server, bypassing the CDN in the process, which would give us an IPv6 presence, but I don't see a particularly compelling need for this. You're welcome to state your case, though, I could be persuaded if I'm wrong.

[miyurusankalpa]

Most people will not notice it due to happy eyeballs. I noticed it only because all my servers are IPv6 only.

The CDN not supporting IPv6 is clearly not your problem and it can be enabled once they support it.

However phpmyadmin.net connection refusing issue is still not solved. This causes browser to wait sometime to fallback to v4 address when the user is dual stacked.

miyuru@MIYURU-LAP:/tmp$ wget phpmyadmin.net
--2020-10-16 18:37:48--  http://phpmyadmin.net/
Resolving phpmyadmin.net (phpmyadmin.net)... 2a01:4f8:13b:15a3::2, 94.130.222.149
Connecting to phpmyadmin.net (phpmyadmin.net)|2a01:4f8:13b:15a3::2|:80... failed: Connection refused.
Connecting to phpmyadmin.net (phpmyadmin.net)|94.130.222.149|:80... connected.

[williamdes]

Most people will not notice it due to happy eyeballs. I noticed it only because all my servers are IPv6 only.

The CDN not supporting IPv6 is clearly not your problem and it can be enabled once they support it.

However phpmyadmin.net connection refusing issue is still not solved. This causes browser to wait sometime to fallback to v4 address when the user is dual stacked.

miyuru@MIYURU-LAP:/tmp$ wget phpmyadmin.net
--2020-10-16 18:37:48--  http://phpmyadmin.net/
Resolving phpmyadmin.net (phpmyadmin.net)... 2a01:4f8:13b:15a3::2, 94.130.222.149
Connecting to phpmyadmin.net (phpmyadmin.net)|2a01:4f8:13b:15a3::2|:80... failed: Connection refused.
Connecting to phpmyadmin.net (phpmyadmin.net)|94.130.222.149|:80... connected.

I see one quick hack, add CloudFlare in front of the website ^^

[ibennetch]

I'll do some tweaks to the DNS and web server tonight and see if that improves this for you :)

[ibennetch]

I've looked in to this quite a bit more and don't think I can split the DNS record for www.phpmyadmin.net and keep IPv4 on the CDN while moving the IPv6 address to the web server directly. I may be mistaken and will keep looking at that.

I have redirected phpmyadmin.net on IPv6 and that address should be working correctly now.

Thanks.

[williamdes]

I may be mistaken and will keep looking at that.

I double checked, using a CNAME you are right it is not possible.

[ibennetch]

Thanks William!

[williamdes]

I moved this issue here to clean out all pure infrastructure tasks from our main repository and added a infrastructure label to have them in one group.

[miyurusankalpa]

It works now. Thanks @ibennetch.

miyuru@MIYURU-LAP:/tmp$ wget https://phpmyadmin.net
--2020-10-18 12:07:10--  https://phpmyadmin.net/
Resolving phpmyadmin.net (phpmyadmin.net)... 2a01:4f8:13b:15a3:1::10, 94.130.222.149
Connecting to phpmyadmin.net (phpmyadmin.net)|2a01:4f8:13b:15a3:1::10|:443... connected.

I will be closing this issue now as the primary issue is fixed and the other problems are related to CDN77.