> For the complete documentation index, see [llms.txt](https://t1t.gitbook.io/t1c-js-guide-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t1t.gitbook.io/t1c-js-guide-v3/3.7.x/miscellaneous/troubleshooting/changing-device-date-time.md). # Changing Device date/time Issues related to device time not in sync ## Introduction The connector can only work when the device date/time is correctly set. This is due to the security applied on exchanged tokens and keys. When a connector has been installed on a device, at a moment which is in the past (other day/time), this results in the connector not working, even though the date/time has been set correctly on the system (post-installation). ### Solution To solve this problem the followin steps need to be executed: * remove all device related keys * restart the connector #### Windows Go to the installation folder of the connector: `%localappdata%/Trust1Connector` Delete all security relate files (selected below):

Those files are: * device.priv * device.pub * device\_der.priv * device\_der.pub * device\_x509\_der.pub * ds-ssl.json * ds-txs.bck {% hint style="info" %} Those files will be automatically generated by the connector after the next step {% endhint %} Use the terminal to open the connector installation folder: `cd ~/Library/Application\ Support/Trust1Team/Trust1Connector` Execute the t1c-launch to restart `./t1c-launch --restart` The process will be stopped, and restarted. The 't1c-launch' process must stop running, and the new processes will trigger the re-generation of the new keys. Due to this action, the device performs a new registration to the Distribution service, this can be verified in the **api.log** file (in the /Logs folder) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://t1t.gitbook.io/t1c-js-guide-v3/3.7.x/miscellaneous/troubleshooting/changing-device-date-time.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.