Answers.Body: <p>In Craft 3 and upwards you should have a vendor folder that is created and updated with composer. You would do the update locally (I recommend docker and ddev), which will update composer.json, composer.lock and the files in the vendor folder. You can do this update via command line (which will be easily accessible if you use ddev) or in the backend.</p>
  <p>If you update via FTP, make sure that you replace composer.json and composer.lock and the vendor folder on the server. That should update Craft. After you replaced them, you might need to migrate the database. You can do this by going to the backend (if you have no access to a command line).</p>
  <p>In your concrete case I'd do the following:</p>
  <ul>
  <li>download a database backup from the Utilities Section</li>
  <li>download the whole project via FTP (if you do not have access to a Git Repository)</li>
  <li>make the project run locally with ddev</li>
  <li>import the database you downloaded before into the database created by ddev</li>
  <li>do the update locally via the command line (<code>ddev craft update all</code>)</li>
  <li>test if everything works fine</li>
  <li>upload composer.json, composer.lock and vendor folder via FTP</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-30T13:35:49.130Z
Answers.Text: Thank you for the information.  I'm going to give this a try today and will report back.
Answers.UserDisplayName: Jake1293
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-09T13:10:07.947Z
Answers.Text: Did it work @Jake1293?
Answers.UserDisplayName: Max Strebel
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-12T13:03:49.910Z
Answers.Text: Unfortunately, it did not. I tried updating the local site and it led down a rabbit hole of errors. Resolving one would only lead to another, and all of them led to a broken site. :(
Answers.UserDisplayName: Jake1293
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-29T11:16:36.997Z
Answers.LastActivityDate: 2023-12-29T14:18:05.543Z
Answers.LastEditDate: 2023-12-29T14:18:05.543Z
Answers.UserDisplayName: Max Strebel
Body: <p>I'm currently using Craft CMS 3.7.9. When I go into Utilities -&gt; Updates (which shows a 5 so there must be updates), a red message appears at the top that says &quot;A server error has occurred&quot; and nothing else loads up on the page besides the spinner graphic. In the console, I see a 404 error for &quot;/index.php?p=admin/actions/app/cache-updates:1&quot;.</p>
  <p><a href="https://craftcms.com/docs/2.x/updating.html#manually-updating" rel="nofollow noreferrer">According to the documentation</a>, I should be able to download the latest version of Craft CMS and install it manually by replacing the /craft/app/ folder. However, when I log in to the server via FTP, I see neither a /craft/ nor an /app/ directory anywhere. In the server root all I see is cache, config, etc, hold, logs, mail, modules, perl5, public_html, ssl, storage, templates, tmp, vendor, and web.  No /craft/ or /app/ directory exists within any of them.</p>
  <p>Edit: I see the documentation linked above is for versions 2.x. The <a href="https://craftcms.com/docs/3.x/updating.html" rel="nofollow noreferrer">3.x documentation</a> indicates I can update via command line, which I don't have access to.</p>
  <p>Does anyone know how to resolve the error I'm seeing on the Updates page? Your help is greatly appreciated.</p>
  
Tags: <craft3><error><updates><404><manual-updates>
Title: Can't Update CraftCMS
ThreadText: # Can't Update CraftCMS
  
  (Asked by: username_0 on 2023-12-29)
  
  I'm currently using Craft CMS 3.7.9. When I go into Utilities -> Updates (which shows a 5 so there must be updates), a red message appears at the top that says "A server error has occurred" and nothing else loads up on the page besides the spinner graphic. In the console, I see a 404 error for "/index.php?p=admin/actions/app/cache-updates:1".
  
  [According to the documentation](https://craftcms.com/docs/2.x/updating.html#manually-updating), I should be able to download the latest version of Craft CMS and install it manually by replacing the /craft/app/ folder. However, when I log in to the server via FTP, I see neither a /craft/ nor an /app/ directory anywhere. In the server root all I see is cache, config, etc, hold, logs, mail, modules, perl5, public\_html, ssl, storage, templates, tmp, vendor, and web. No /craft/ or /app/ directory exists within any of them.
  
  Edit: I see the documentation linked above is for versions 2.x. The [3.x documentation](https://craftcms.com/docs/3.x/updating.html) indicates I can update via command line, which I don't have access to.
  
  Does anyone know how to resolve the error I'm seeing on the Updates page? Your help is greatly appreciated.
  
  **Tags:** craft3, error, updates, 404, manual-updates
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-12-29. Score: 3
  
  In Craft 3 and upwards you should have a vendor folder that is created and updated with composer. You would do the update locally (I recommend docker and ddev), which will update composer.json, composer.lock and the files in the vendor folder. You can do this update via command line (which will be easily accessible if you use ddev) or in the backend.
  
  If you update via FTP, make sure that you replace composer.json and composer.lock and the vendor folder on the server. That should update Craft. After you replaced them, you might need to migrate the database. You can do this by going to the backend (if you have no access to a command line).
  
  In your concrete case I'd do the following:
  
  * download a database backup from the Utilities Section
  * download the whole project via FTP (if you do not have access to a Git Repository)
  * make the project run locally with ddev
  * import the database you downloaded before into the database created by ddev
  * do the update locally via the command line (`ddev craft update all`)
  * test if everything works fine
  * upload composer.json, composer.lock and vendor folder via FTP
  
  > **Comments:**
  > **username_0**: Thank you for the information.  I'm going to give this a try today and will report back.  
  > **username_1**: Did it work @username_0?  
  > **username_0**: Unfortunately, it did not. I tried updating the local site and it led down a rabbit hole of errors. Resolving one would only lead to another, and all of them led to a broken site. :(  
  
  ---
  
  