<p>Updated using <code>composer update craftcms/cms</code> </p>

CC BY-SA 3.0
2017-12-08T14:21:42.890Z
I tried this and was getting: Problem 1
    - Can only install one of: craftcms/server-check[1.1.0, 1.0.17]. So I needed to just run `composer update` to update dependencies too. It worked for me.
Johann Dyck
CC BY-SA 3.0
2017-12-07T12:11:03.880Z
2017-12-07T12:11:03.880Z
Daimz
<p>You can use this article to help debug 504 Gateway Timeout errors that can be common when updating Craft, because those tend to be longer running operations: <a href="https://craftcms.com/support/504-gateway-timed-out-error" rel="nofollow noreferrer">https://craftcms.com/support/504-gateway-timed-out-error</a></p>

<p><a href="https://craftcms.stackexchange.com/a/23093/57">Your solution</a> works because PHP timeouts from the command line are generally much more forgiving that PHP timeouts from a web browser.</p>

<p>Craft 3 uses <a href="https://getcomposer.org" rel="nofollow noreferrer">Composer</a> for its updating needs (for itself and for plugins).  Composer has a tendency to be the opposite of fast, so you might want to go ahead and bump things like your php.ini file's <code>max_execution_time</code> for future updates if you plan on doing it from the Control Panel.</p>

CC BY-SA 3.0
2017-12-07T23:24:24.040Z
2017-12-07T23:24:24.040Z
Brad Bell
<p>I got a notification in the Craft 3 beta versions I have been working on to upgrade to 3.0.0 RC1. I clicked update and it began updating only the throw the following error. Any ideas what may have happened?</p>

<pre><code>Status: Gateway Time-out

Response: &lt;html&gt;
&lt;head&gt;&lt;title&gt;504 Gateway Time-out&lt;/title&gt;&lt;/head&gt;
&lt;body bgcolor="white"&gt;
&lt;center&gt;&lt;h1&gt;504 Gateway Time-out&lt;/h1&gt;&lt;/center&gt;
&lt;hr&gt;&lt;center&gt;nginx/1.12.2&lt;/center&gt;
&lt;/body&gt;
&lt;/html&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
&lt;!-- a padding to disable MSIE and Chrome friendly error page --&gt;
</code></pre>

<p>If it's of any help, this is a composer install using Valet to run.</p>

CC BY-SA 3.0
2017-12-07T12:10:23.970Z
I manage to solve the issue by using composer to upgrade, but first had to delete the composer lock file.
Daimz
<craft3><upgrades><timeout>
Upgrade to 3.0.0 RC1 failed due to 504 Gateway Time-out
# Upgrade to 3.0.0 RC1 failed due to 504 Gateway Time-out

(Asked by: username_0 on 2017-12-07)

I got a notification in the Craft 3 beta versions I have been working on to upgrade to 3.0.0 RC1. I clicked update and it began updating only the throw the following error. Any ideas what may have happened?
Status: Gateway Time-out

Response: 
504 Gateway Time-out

504 Gateway Time-out
nginx/1.12.2









If it's of any help, this is a composer install using Valet to run.

**Tags:** craft3, upgrades, timeout

> **Comments:**
> **username_0**: I manage to solve the issue by using composer to upgrade, but first had to delete the composer lock file.  

---

## 2 answers

### Answer by username_0 on 2017-12-07. Score: 2

Updated using `composer update craftcms/cms`

> **Comments:**
> **username_1**: I tried this and was getting: Problem 1     - Can only install one of: craftcms/server-check[1.1.0, 1.0.17]. So I needed to just run `composer update` to update dependencies too. It worked for me.  

---

### Answer by username_2 on 2017-12-07. Score: 1

You can use this article to help debug 504 Gateway Timeout errors that can be common when updating Craft, because those tend to be longer running operations: <https://craftcms.com/support/504-gateway-timed-out-error>

[Your solution](https://craftcms.stackexchange.com/a/23093/57) works because PHP timeouts from the command line are generally much more forgiving that PHP timeouts from a web browser.

Craft 3 uses [Composer](https://getcomposer.org) for its updating needs (for itself and for plugins). Composer has a tendency to be the opposite of fast, so you might want to go ahead and bump things like your php.ini file's `max_execution_time` for future updates if you plan on doing it from the Control Panel.


---

