Unable To Access Orchestrator Site And Is Stuck In After Login

News Knowledge Base
1

Unable to access the Orchestrator site and it is stuck in after the login.

Error Message:

main.11c7064166a5b065.js?version=2022.10.5:1 Error: exp is in the past:1689835471

at r.validateJwtAttributes (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2284045)

at vendor.95480f6bc57315fb.js?version=2022.10.5:1:2095708

at _t.value (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2666592)

at Object.onInvoke (vendor.95480f6bc57315fb.js?version=2022.10.5:1:3204182)

at _t.value (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2666526)

at Lt.value (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2660331)

at vendor.95480f6bc57315fb.js?version=2022.10.5:1:2678163

at _t.value (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2667315)

at Object.onInvokeTask (vendor.95480f6bc57315fb.js?version=2022.10.5:1:3203982)

at _t.value (vendor.95480f6bc57315fb.js?version=2022.10.5:1:2667231)




Root Cause: If Orchestrator server and database server have different time, then sync with the current time as per the Orchestrator server timezone so that client machine and Orchestrator server all are in the same GEO current time and the token will be valid as per the expiration time.


Resolution: Steps to perform in the Client browser,

  1. Click on the three-vertical-dot icon in the upper right of Google Chrome.
  2. Select More Tools.
  3. Select Developer Tools.
  1. The tools will usually be docked on the right or bottom of your screen. Make sure that the Console is selected:
  1. Check if the below error is thrown and if the JWT token is already expired when it comes to the client machine.