Answers.Body: <p>There are a billion reasons for WP/Civi timeouts. To start from, a few notes:</p>
  <ul>
  <li><strong>300MB PHP RAM</strong>: I'd make it 512Mb or 1G:  the latter requires at least 4G on the server</li>
  <li><strong>500Mb SQL RAM</strong>: well, it's actually not that much: try this <a href="https://github.com/major/MySQLTuner-perl" rel="nofollow noreferrer">https://github.com/major/MySQLTuner-perl</a> to check DB internals: it worth following recommendations the script provides.</li>
  <li><strong>max execution time of 500</strong> : afraid this one does not make sense nor any difference here at all. You might want to stick to 120.</li>
  </ul>
  <p>Also, have you checked:</p>
  <ul>
  <li>CiviCRM Logs</li>
  <li>WP Debug output</li>
  <li>PHP error logs</li>
  <li>Web server [Apache?] error logs</li>
  <li>MySQL error logs?</li>
  </ul>
  <p>Your answer is somewhere in the logs above.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-21T23:29:54.117Z
Answers.Text: Thank you, yurg. This at least points me in the right direction. I'm marking your answer as "accepted," not because all my problems have suddenly been fixed but because your answer is at least helping me figure out what to focus on.
Answers.UserDisplayName: Bruce Hooke
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-22T10:33:58.157Z
Answers.Text: Thank you @BruceHooke, please keep us updated if possible: maybe someone else will find your follow-up useful ;-)
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-21T08:50:51.823Z
Answers.LastActivityDate: 2022-07-21T11:38:35.087Z
Answers.LastEditDate: 2022-07-21T11:38:35.087Z
Answers.UserDisplayName: yurg
Body: <p>I have CiviCRM installed on a development WordPress site and I keep having problems with timeout errors. This is a VPS server with a VPS SQL account. The server has 2000MB of RAM and the SQL account has another 500MB of RAM. This is the only website running on this VPS. I have configured PHP to have a memory limit of 300MB and a max execution time of 500. I have confirmed in WordPress that these settings are recognized by WordPress. I'm trying to figure out what to do next to troubleshoot what needs to be adjusted to address the timeout errors. CiviCRM version 5.44.0. WordPress version 6.0.1</p>
  <p>Thanks!</p>
  
Tags: <wordpress>
Title: CiviCRM - WordPress - Frequent timeout errors
ThreadText: # CiviCRM - WordPress - Frequent timeout errors
  
  (Asked by: username_0 on 2022-07-20)
  
  I have CiviCRM installed on a development WordPress site and I keep having problems with timeout errors. This is a VPS server with a VPS SQL account. The server has 2000MB of RAM and the SQL account has another 500MB of RAM. This is the only website running on this VPS. I have configured PHP to have a memory limit of 300MB and a max execution time of 500. I have confirmed in WordPress that these settings are recognized by WordPress. I'm trying to figure out what to do next to troubleshoot what needs to be adjusted to address the timeout errors. CiviCRM version 5.44.0. WordPress version 6.0.1
  
  Thanks!
  
  **Tags:** wordpress
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-07-21. Score: 0 | Accepted answer
  
  There are a billion reasons for WP/Civi timeouts. To start from, a few notes:
  
  * **300MB PHP RAM**: I'd make it 512Mb or 1G: the latter requires at least 4G on the server
  * **500Mb SQL RAM**: well, it's actually not that much: try this <https://github.com/major/MySQLTuner-perl> to check DB internals: it worth following recommendations the script provides.
  * **max execution time of 500** : afraid this one does not make sense nor any difference here at all. You might want to stick to 120.
  
  Also, have you checked:
  
  * CiviCRM Logs
  * WP Debug output
  * PHP error logs
  * Web server [Apache?] error logs
  * MySQL error logs?
  
  Your answer is somewhere in the logs above.
  
  > **Comments:**
  > **username_0**: Thank you, username_1. This at least points me in the right direction. I'm marking your answer as "accepted," not because all my problems have suddenly been fixed but because your answer is at least helping me figure out what to focus on.  
  > **username_1**: Thank you @username_0, please keep us updated if possible: maybe someone else will find your follow-up useful ;-)  
  
  ---
  
  