Can't access pkg.julialang.org

I can’t access pkg.julialang.org. It redirect me to https://cn-northeast.pkg.juliacn.com/, which is broken several months ago.

(@v1.8) pkg> registry up
┌ Warning: could not download https://pkg.julialang.org/registries
│   exception = HTTP/2 301 (OpenSSL/3.1.4: error:0A00010B:SSL routines::wrong version number) while requesting https://pkg.julialang.org/registries
└ @ Pkg.Registry /var/tmp/portage/dev-lang/julia-1.8.5-r1/work/julia-1.8.5/usr/share/julia/stdlib/v1.8/Pkg/src/Registry/Registry.jl:68
    Updating registry at `~/.julia/registries/General.toml`

output of curl -IvL:

* Host pkg.julialang.org:443 was resolved.
* IPv6: 2a04:4e42:12::729
* IPv4: 146.75.114.217
*   Trying 146.75.114.217:443...
* Connected to pkg.julialang.org (146.75.114.217) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=pkg.julialang.org
*  start date: Apr 12 16:45:25 2023 GMT
*  expire date: May 13 16:45:24 2024 GMT
*  subjectAltName: host "pkg.julialang.org" matched cert's "pkg.julialang.org"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Atlas R3 DV TLS CA 2023 Q2
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://pkg.julialang.org/registries
* [HTTP/2] [1] [:method: HEAD]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: pkg.julialang.org]
* [HTTP/2] [1] [:path: /registries]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> HEAD /registries HTTP/2
> Host: pkg.julialang.org
> User-Agent: curl/8.5.0
> Accept: */*
> 
< HTTP/2 301 
HTTP/2 301 
< server: Varnish
server: Varnish
< retry-after: 0
retry-after: 0
< location: https://cn-northeast.pkg.juliacn.com/registries
location: https://cn-northeast.pkg.juliacn.com/registries
< x-geo-continent: AS
x-geo-continent: AS
< x-geo-country: CN
x-geo-country: CN
< x-geo-region: BJ
x-geo-region: BJ
< accept-ranges: bytes
accept-ranges: bytes
< date: Thu, 21 Dec 2023 12:32:58 GMT
date: Thu, 21 Dec 2023 12:32:58 GMT
< via: 1.1 varnish
via: 1.1 varnish
< x-served-by: cache-hkg17935-HKG
x-served-by: cache-hkg17935-HKG
< x-cache: HIT
x-cache: HIT
< x-cache-hits: 0
x-cache-hits: 0
< x-timer: S1703161979.914725,VS0,VE0
x-timer: S1703161979.914725,VS0,VE0
< content-length: 0
content-length: 0

< 
* Connection #0 to host pkg.julialang.org left intact
* Issue another request to this URL: 'https://cn-northeast.pkg.juliacn.com/registries'
* Host cn-northeast.pkg.juliacn.com:443 was resolved.
* IPv6: (none)
* IPv4: 124.70.44.226
*   Trying 124.70.44.226:443...
* Connected to cn-northeast.pkg.juliacn.com (124.70.44.226) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cn-northeast.pkg.juliacn.com:443 
* Closing connection
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cn-northeast.pkg.juliacn.com:443 

try force it to use https://us-east.pkg.julialang.org

I mean, Since cn-northeast.pkg.juliacn.com is broken, it shouldn’t be redirected. We should make things work by default.

4 Likes

The same problem. Solved by forcing it to use the Korean server. But I totally agree that it should be officially fixed.

Does anyone know why it is broken?