is there a known issue with the ipv4 servers hosting various metabrainz sites, including musicbrainz.org, static.metabrainz.org and coverartarchive.org? I have to manually redirect these domains to their ipv6 addresses to be able to connect to them
2024-04-14 10515, 2024
FichteFoll
curl complains with `curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to musicbrainz.org:443` when simply running `curl musicbrainz.org` (also when forcing ipv4 via `-4`) but it works when forcing ipv6 (via `-6`)
2024-04-14 10537, 2024
FichteFoll
firefox also uses ipv4 by default, leading to PR_END_OF_FILE_ERROR errors for all affected domains, while chromium uses ipv6 and works
2024-04-14 10554, 2024
FichteFoll
I've had this issue with PR_END_OF_FILE_ERROR for quite a while (at least half a year) but never bother to looked into it further because it was hard to find any relevant information about it. I only found out about the difference between ipv4 and ipv6 by coincidence
2024-04-14 10545, 2024
FichteFoll
I can also mention this on the forum or the issue tracker, if desired
2024-04-14 10511, 2024
FichteFoll
apparently someone else was unable to reproduce this, so it seems likely this is a problem with my openssl or similar
2024-04-14 10536, 2024
FichteFoll
also works fine from my phone
2024-04-14 10522, 2024
FichteFoll
well, I give up. everything points to it being a problem with my system only, but I have no idea why or how to fix it properly. I'll leave the ipv6s pinned in my hosts file until I miraculously find someone else with an idea
FichteFoll: can you post about the issue you have on forums? Please indicate your platform and openssl version. We'll see if more people share the exact issue, perhaps we'll find a pattern that will head us to a solution.
2024-04-14 10537, 2024
FichteFoll
all right
2024-04-14 10538, 2024
zas
I don't exclude a misconfiguration on our side, ssl stuff is complex and ever evolving
2024-04-14 10538, 2024
zas
you are using a recent version of openssl, perhaps that's something new in it (or just a bug), hard to tell at this point
2024-04-14 10550, 2024
zas
atj: ^^ any idea?
2024-04-14 10515, 2024
FichteFoll
it's definitely a very weird issue because I remember already having this issue on my private machine while my work machine could connect properly. Both are using Arch and updated every other week or so
2024-04-14 10526, 2024
atj
FichteFoll: I use Arch and have IPv6 at don't have this issue
2024-04-14 10531, 2024
FichteFoll
so just the recent version seems unlikely
2024-04-14 10533, 2024
atj
s/at/and
2024-04-14 10517, 2024
atj
FichteFoll: can you try running `strace openssl s_client -servername musicbrainz.org -connect musicbrainz.org:443 -prexit -4` and paste the log? (probably very long)
FichteFoll: thanks, nothing obviously wrong in that trace. the "unexpected eof" SSL error brings up some issues about bugs due to changes in openssl 3.0 https://github.com/openssl/openssl/issues/18866
2024-04-14 10527, 2024
atj
however that doesn't make sense if it magically works with IPv6
