JuliaPro1.5.0: could not download https://pkg.juliahub.com/registries

Today I installed the new version of JuliaPro, but met the issue

 Warning: could not download https://pkg.juliahub.com/registries
└ @ Pkg.Types D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.5\Pkg\src\Types.jl:951

what could be the reason? thanks.

Are you able to download https://pkg.juliahub.com/registries from the commandline with curl for example?

No, it says
curl : 401 Authorization Required

I checked that I have an auth.toml file in .julia/servers/pkg.juliahub.com. Does the error mean that this file is not valid?

This issue is now fixed on the server side, can you try updating your registry now? Please make sure you have a valid .julia/servers/pkg.juliahub.com/auth.toml

3 Likes

it worked. Thank you!

1 Like

I seem to have the same problem from the command line

~ e% exec '/Applications/Julia-1.5.app/Contents/Resources/julia/bin/julia'
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.5.2 (2020-09-23)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> 

(@v1.5) pkg> update Pluto
   Updating registry at `~/.julia/registries/General`
┌ Warning: could not download https://pkg.julialang.org/registries
└ @ Pkg.Types /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.5/Pkg/src/Types.jl:951
   Updating registry at `~/.julia/registries/JuliaComputingRegistry`
No Changes to `~/.julia/environments/v1.5/Project.toml`
No Changes to `~/.julia/environments/v1.5/Manifest.toml`

However, I have a ~/.julia/servers/pkg.juliahub.com/auth.toml
It looks legit, how can I verify that it’s valid, or update it if it’s not?

OK, I found the solution. Go to https://pkg.juliacomputing.com/auth in a browser, and authenticate. A file is downloaded; in my case it was named token.toml so I renamed it to auth.toml and moved into the directory ~/.julia/servers/pkg.juliahub.com/ replacing the old version, which must have been expired. Why is this so hard?

1 Like

Hi,

I have the same problem and managed to download the file you mentioned. However, I don’t have the directory ~/.julia/servers. Should I create one manually?

We’re looking into why this is happening. Yes, of you create ~/.julia/servers/pkg.juliahub.com/ and put the auth.toml file in it, that should work.

2 Likes

Thank you for your confirmation. I hope this works out well. On top of this issue, FYI server in us-east is often returned 502 Bad Gateway, if you think this is what also may cause this issue.

That’s an entirely different server, so it shouldn’t have any effect. The us-east.pkg.julialang.org server is a Julia community server and doesn’t require authentication.

1 Like

I don’t understand the approach neither. I am neither a package maintainer, nor a Pro/member of JuliaTeam. Why am I required to have the file auth.toml?

The warning I got is

(@v1.5) pkg> update
   Updating registry at `~/.julia/registries/General`
┌ Warning: could not download https://pkg.julialang.org/registries
└ @ Pkg.Types /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/Pkg/src/Types.jl:951

The file is required because JuliaPro uses an authenticated package server, pkg.juliahub.com (maintained by Julia Computing, like JuliaPro itself). This server supports integration with https://JuliaHub.com which requires knowing who you are (for example, imminently forthcoming ability to send compute from you JuliaPro to the cloud, with parallelization). For that it needs an auth.toml file. JuliaPro should be generating that file for you automatically and saving it to the right place.

In order to authenticate you, there is a flow where you need to visit a web page on https://JuliaHub.com in your browser to prove that you are who you say you are. It is possible that is not happening for some reason—maybe JuliaPro does not have a way to open a browser window for you, or the window is being suppressed when it does. Saving that file yourself is not normal and indicates that something is wrong with the normal auth flow on your system. More detail about what does and doesn’t happen and about your system would be helpful to figure out what is going wrong. If you’re comfortable providing it here, that’s good, otherwise you can send DMs to me and I will make sure the JuliaPro/Hub team gets them.

it certainly makes sense for JuliaPro users, but I am currently not. To clarify, my case is “Warning: could not download https://pkg.julialang.org/registries” and thus can’t get packages updated. Maybe I should start a new thread, but is there any chance the two issues actually be fixed, if any bugs, at the same time perhaps (as it refers to the same line stdlib/v1.5/Pkg/src/Types.jl:951)?

That’s an entirely different matter and unrelated to what this thread is about. The US East community package server has been having some maintenance issues, which will get looked at soon. In the meantime, you can try setting JULIA_PKG_SERVER=us-west.pkg.julialang.org in your shell.

3 Likes

Thanks! My case closed.

I hadn’t initially noticed this but this is not attempting to connect to pkg.juliahub.com but rather pkg.julialang.org, so the auth stuff is not irrelevant: no auth is being done here. Given that, I’m not sure why downloading the auth.toml file manually would change anything…

1 Like

i’m also experiencing this issue