Answers.Body: <p>The warning is because the timezone of the server does not match with the timezone set in MySQL. We had similar warning and after setting the timezone in both Centos &amp; MySQL, the warning is not displayed anymore.</p>
  <h1>Additional Info:</h1>
  <p>This is how we corrected/fixed the timezones, if it helps. The below instructions are for setting timezone to GMT, you need to use your timezone if you want to use the below instructions.</p>
  <p><strong>Setting the timezone in CentOS</strong></p>
  <p>Check the date and timezone</p>
  <pre><code>[root@my-server ~]# date
  Mon Nov 24 10:27:14 CET 2014
  </code></pre>
  <p>The above is incorrect. We need to set GMT for Europe/London</p>
  <p>Fix the timezone</p>
  <pre><code>[root@my-server ~]# rm /etc/localtime
  [root@my-server ~]# ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
  </code></pre>
  <p>Now check the date and timezone again</p>
  <pre><code>[root@my-server ~]# date
  Mon Nov 24 09:30:14 GMT 2014
  </code></pre>
  <p><strong>Setting the timezone in MySQL</strong></p>
  <p>Check the timezone in MySQL</p>
  <pre><code>mysql&gt; SELECT @@global.time_zone;
  +-----------------------------+
  | @@global.time_zone          |
  +-----------------------------+
  | SYSTEM                      |
  +-----------------------------+
  1 row in set (0.00 sec)
  </code></pre>
  <p>Set timezone '+00:00' for GMT</p>
  <pre><code>mysql&gt; SET GLOBAL time_zone = '+00:00';
  Query OK, 0 rows affected (0.00 sec)
  </code></pre>
  <p>Now check the timezone again in MysSQL</p>
  <pre><code>mysql&gt; SELECT @@global.time_zone;
  +-----------------------------+
  | @@global.time_zone          |
  +-----------------------------+
  | +00:00                      |
  +-----------------------------+
  1 row in set (0.00 sec)
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T14:25:57.827Z
Answers.LastActivityDate: 2015-04-16T14:25:57.827Z
Answers.LastEditDate: 2020-06-17T09:00:50.810Z
Answers.UserDisplayName: Ghost
Answers.Body: <p>In my experience with this, you can modify the default timezone setting for your CMS. Not sure how to do this in Joomla, but there are UI options for this in both Wordpress and Drupal so I would imagine that Joomla offers a similar setting.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-23T21:54:04.353Z
Answers.Text: Yep, I just had a Wordpress site giving this error -- it didn't have the timezone set in the Wordpress admin UI.
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T09:10:42.077Z
Answers.LastActivityDate: 2015-04-16T09:10:42.077Z
Answers.UserDisplayName: Graham
Body: <p>I currently have a warning on Environment settings. Timestamps reported by MySQL and PHP are mismatched.</p>
  
Tags: <joomla><error><timezone><timestamp>
Title: How do I set the time zones in order to correct mismatched Timestamps for MySQL and PHP?
ThreadText: # How do I set the time zones in order to correct mismatched Timestamps for MySQL and PHP?
  
  (Asked by: username_0 on 2015-04-16)
  
  I currently have a warning on Environment settings. Timestamps reported by MySQL and PHP are mismatched.
  
  **Tags:** joomla, error, timezone, timestamp
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-04-16. Score: 6
  
  The warning is because the timezone of the server does not match with the timezone set in MySQL. We had similar warning and after setting the timezone in both Centos & MySQL, the warning is not displayed anymore.
  
  # Additional Info:
  
  This is how we corrected/fixed the timezones, if it helps. The below instructions are for setting timezone to GMT, you need to use your timezone if you want to use the below instructions.
  
  **Setting the timezone in CentOS**
  
  Check the date and timezone
  
  ```
  [root@my-server ~]# date
  Mon Nov 24 10:27:14 CET 2014
  
  ```
  
  The above is incorrect. We need to set GMT for Europe/London
  
  Fix the timezone
  
  ```
  [root@my-server ~]# rm /etc/localtime
  [root@my-server ~]# ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
  
  ```
  
  Now check the date and timezone again
  
  ```
  [root@my-server ~]# date
  Mon Nov 24 09:30:14 GMT 2014
  
  ```
  
  **Setting the timezone in MySQL**
  
  Check the timezone in MySQL
  
  ```
  mysql> SELECT @@global.time_zone;
  +-----------------------------+
  | @@global.time_zone          |
  +-----------------------------+
  | SYSTEM                      |
  +-----------------------------+
  1 row in set (0.00 sec)
  
  ```
  
  Set timezone '+00:00' for GMT
  
  ```
  mysql> SET GLOBAL time_zone = '+00:00';
  Query OK, 0 rows affected (0.00 sec)
  
  ```
  
  Now check the timezone again in MysSQL
  
  ```
  mysql> SELECT @@global.time_zone;
  +-----------------------------+
  | @@global.time_zone          |
  +-----------------------------+
  | +00:00                      |
  +-----------------------------+
  1 row in set (0.00 sec)
  
  ```
  
  
  ---
  
  ### Answer by username_2 on 2015-04-16. Score: 3
  
  In my experience with this, you can modify the default timezone setting for your CMS. Not sure how to do this in Joomla, but there are UI options for this in both Wordpress and Drupal so I would imagine that Joomla offers a similar setting.
  
  > **Comments:**
  > **username_3**: Yep, I just had a Wordpress site giving this error -- it didn't have the timezone set in the Wordpress admin UI.  
  
  ---
  
  