# Gateway timezone doesn't match OS

**URL:** <https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912>\
**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:** 1\
**Showing post:** 6

<div class="post-metadata">

**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")

</div>

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.

---

_[View the full topic](https://forum.inductiveautomation.com/t/gateway-timezone-doesnt-match-os/33912)._