# Gateway timezone doesn't match OS **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [April 14, 2020, 11:54am UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912 "2020-04-14T11:54:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [April 14, 2020, 11:54am UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/1 "2020-04-14T11:54:10Z")
Using v8.0.10, the server is set for eastern time, the time in the OS is correct. The system timezone in Ignition is central time. Besides restarting the gateway, how can I update or sync this? ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [April 14, 2020, 4:34pm UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/2 "2020-04-14T16:34:41Z")
I had a chance to reboot the server, the timezone is now correct and matches the OS, but the time is still wrong. The OS time is correct, the current date time in Ignition is an hour behind. How can I fix this? ---
**Author:** ![Phil\_B](https://avatars.discourse-cdn.com/v4/letter/p/c89c15/32.png) [@Phil\_B](https://forum.inductiveautomation.com/u/Phil_B)\ **Post date:** [April 14, 2020, 4:39pm UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/3 "2020-04-14T16:39:38Z")
When i see this it is usually because i am in a different timezone than the server. Ignition corrects for the difference. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [April 14, 2020, 8:13pm UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/4 "2020-04-14T20:13:59Z")
I’m in the same timezone. I restarted the server and then each client and it corrected. Not something I wanted to do, but at least it’s fixed. Hopefully I don’t see that again. ---
**Author:** ![Phil\_B](https://avatars.discourse-cdn.com/v4/letter/p/c89c15/32.png) [@Phil\_B](https://forum.inductiveautomation.com/u/Phil_B)\ **Post date:** [April 14, 2020, 8:28pm UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/5 "2020-04-14T20:28:55Z")
Ahh, the clients might have had the timezone cached from when they were first started (dont know for sure buts thats my guess). glad to hear its good to go. ---
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [April 14, 2020, 8:44pm UTC](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912/6 "2020-04-14T20:44:47Z")
Yeah, I ran into something like this a while back and went through the same steps: > [@Gateway time doesn't match timezone](http://forum.inductiveautomation.com/t/gateway-time-doesnt-match-timezone/22103/2): > > We just ran into this on a new computer. Ignition was installed and started up on a Windows 10 computer set to the wrong timezone (one hour earlier) and then the timezone was set correctly in Windows. Ignition gateway status page showed the correct time for the new timezone. But Designer–and Vision clients set to use gateway timezone–were showing the correct gateway timezone, but the wrong time. Restarting Ignition gateway did not help. Neither did restarting Windows on the computer running the … I'm not certain whether restarting the gateway was necessary or not. Restarting the clients and designers (if you want them to show the right gateway time) is.