### Author:  [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [August 7, 2024, 11:36am UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/1 "2024-08-07T11:36:48Z")
I get this error:
```plaintext
I, [2024-08-07T11:22:31.056567 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
error Error: https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz: ESOCKETTIMEDOUT
```
~~When I follow the link I see this. No idea if that is relevant..~~
Final error message:
```plaintext
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' failed with return #
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"yarn", "cmd"=>["if [\"$version\" != \"tests-passed\"]; then\n rm -rf app/assets/javascripts/node_modules\nfi", "su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'"]}
bootstrap failed with exit code 1
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 7, 2024, 11:46am UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/2 "2024-08-07T11:46:51Z")
> [@manuel](#):
>
> `https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz`
that’s working for me:
`wget https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz`
btw, do you mean `3.4.0`?
---
### Author:  [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [August 7, 2024, 11:58am UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/3 "2024-08-07T11:58:32Z")
> [@merefield](#):
>
> that’s working for me:
had a colon at the end 🙄
> [@merefield](#):
>
> btw, do you mean `3.4.0`?
dashboard tells me 3.3.0-beta6 is latest..
Just found this topic, will try that:
> [@Error during the update ESOCKETTIMEDOUT registry.yarnpkg.com](https://meta.discourse.org/t/error-during-the-update-esockettimedout-registry-yarnpkg-com/268613):
>
> Trying to update Discourse via the manual procedure git pull ./launcher rebuild app ... ./discourse-doctor shows an error I, [2023-06-16T11:39:43.530890 #1] INFO -- : \> cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' error An unexpected error occurred: "https://registry.yarnpkg.com/date-fns/-/date-fns-2.29.3.tgz: ESOCKETTIMEDOUT". FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfi…
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 7, 2024, 11:59am UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/4 "2024-08-07T11:59:40Z")
> [@manuel](#):
>
> dashboard tells me 3.3.0-beta6 is latest…
That’s odd in itself, should look more like:
---
### Author:  [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [August 7, 2024, 12:01pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/5 "2024-08-07T12:01:03Z")
I see that on another instance as well:
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [August 7, 2024, 12:04pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/6 "2024-08-07T12:04:12Z")
> [@Celebrating Discourse release 3.3](https://meta.discourse.org/t/celebrating-discourse-release-3-3/319189/6):
>
> This was bumped/tagged by mistake. We can’t easily remove the commit, but the tag has now been removed. v3.3.0.beta5 was the final beta version of 3.3, and is identical to 3.3.0 stable.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 7, 2024, 12:12pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/7 "2024-08-07T12:12:05Z")
aah, thanks, missed that.
---
### Author:  [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [August 7, 2024, 12:28pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/8 "2024-08-07T12:28:10Z")
Ok, fixed as per [Stuck on yarn install, Time out](https://meta.discourse.org/t/stuck-on-yarn-install-time-out/227738).
For reference, in `/var/discourse/templates/web.template.yml` I added this block:
```plaintext
- exec:
cd: $home
cmd:
- su discourse -c 'yarn config set network-timeout 600000 -g'
```
before this one is called:
```plaintext
- exec:
cd: $home
hook: yarn
cmd:
- |-
if ["$version" != "tests-passed"]; then
rm -rf app/assets/javascripts/node_modules
fi
- su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
```
But why does it time-out? The solution on the linked topic states that it’s because of the small server specs (Google e2.micro instance, 2 cores, 1 GB RAM). But this is a 4 cores, 6GB VPS.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [August 7, 2024, 12:52pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/9 "2024-08-07T12:52:37Z")
Thanks for sharing the solution @nolo. This isn’t the first time people have hit this problem, so let’s improve things in the default template:
[https://github.com/discourse/discourse\_docker/pull/820](https://github.com/discourse/discourse_docker/pull/820)
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [September 6, 2024, 12:53pm UTC](https://meta.discourse.org/t/error-upgrading-to-3-3-0-beta6-because-of-yarn-timeout/320526/10 "2024-09-06T12:53:12Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.