# Juliaup: Error: Failed to update versions db. Alway safe to just reinstall?

**URL:** https://discourse.julialang.org/t/juliaup-error-failed-to-update-versions-db-alway-safe-to-just-reinstall/125128
**Category:** New to Julia
**Tags:** juliaup
**Created:** [January 23, 2025, 2:48pm UTC](https://discourse.julialang.org/t/juliaup-error-failed-to-update-versions-db-alway-safe-to-just-reinstall/125128 "2025-01-23T14:48:58Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)
#### Post date: [January 23, 2025, 2:48pm UTC](https://discourse.julialang.org/t/juliaup-error-failed-to-update-versions-db-alway-safe-to-just-reinstall/125128/1 "2025-01-23T14:48:58Z")

</div>

I get:

```julia
$ juliaup update
Error: Failed to update versions db.

Caused by:
    ETag header not found in response

```

I get this for many commands, including:

```julia
$ juliaup add 1.11.3

```

Though no error for:

```julia
$ juliaup default 1.11
Configured the default Julia version to be '1.11'.

```

However I start 1.10.6 by default.

I’ve had this error for a while now, just put off fixing, digging into it, since I can manually choose my versions with +1.10 and +1.11.

While writing this post I figured out how to partially fix, by deleting the last PR I had added:

```julia
$ juliaup remove pr56180

```

But after upgrading I now just get newer 1.10.8.

If anyone has an idea how to fix this, edit some config file(?), then let me please let me know. I think it’s always safe to drop a package, juliaup, with apt-get or whatever, and then add again, but likely will not fix, since I think I will keep my config? I can also backup .julia and then remove it, but would like to know the cause.

I’m not new to Julia, nor really juliaup, but put it in that category. Not sure where else, feel free to move it.

> <https://github.com/JuliaLang/juliaup/issues/1021#issuecomment-2439407793>
>
> \`\`\`
> x@x:~$ juliaup update
> Error: Failed to update versions db.
> 
> Caused by:
> … ETag header not found in response
> x@x:~$ juliaup --version
> Juliaup 1.17.4
> \`\`\`
> My internet seems fine (I'm posting this issue from the same internet as I received the error message from).
> 
> If this is a network issue, it should be more clear in the error message. Otherwise it is likely a bug.

```
      nightly Development version 1.12.0-DEV.1575 Update available 
      pr56180 Development version 1.11.1                            
      pr56228 Development version 1.11.1 Update available 
      pr56288 Development version 1.12.0-DEV.1745  

```

I removed all of those even nightly for good measure…

---

<div class="post-metadata">

### Author: ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [January 23, 2025, 6:11pm UTC](https://discourse.julialang.org/t/juliaup-error-failed-to-update-versions-db-alway-safe-to-just-reinstall/125128/2 "2025-01-23T18:11:13Z")

</div>

There is currently a bug when you try to update and have a pr channel installed where the download for that pr has been removed from the server. [Fix unavailable PR channels on Windows by davidanthoff · Pull Request #1155 · JuliaLang/juliaup · GitHub](https://github.com/JuliaLang/juliaup/pull/1155) will fix that, but for now the solution is to just remove that pr channel.

---

<div class="post-metadata">

### Author: ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)
#### Post date: [January 24, 2025, 3:02pm UTC](https://discourse.julialang.org/t/juliaup-error-failed-to-update-versions-db-alway-safe-to-just-reinstall/125128/3 "2025-01-24T15:02:43Z")

</div>

Thanks, I had noticed that PR, but I’m not on Windows, I still thought it might apply more generally. Then might be good to change its title.

I’m in no hurry since I can manually switch. The question still stands from the title, there must be a way to reinstall and wipe the config. That should work too?

Keep up the good work, thanks for it, and in advance. I’ll see if my juliaup will get fixed soon after that PR is merged.

About the two issues, first, on error messages, googling `ETag header not found in response` was not helpful, since nonspecific, not just for juliaup, but `Failed to update versions db` was.

It however doesn’t seem to explain this not working (nor led me to find if there’s an open issue on it or PR, I didn’t search for long…):

```julia
$ juliaup default 1.11
Configured the default Julia version to be '1.11'.

```
