[If you are posting a new bug, please include the following]
2025-01-12-18-54-21-Main.tzlog.txt (2.7 MB)
Try a manual log out and then afterwards log in again.
This seems to have helped some people.
P.S. you should edit your post and remove your email address.
I did. I even rebooted, then loaded the video for processing and went to bed. This morning it was done, but branded.
The logs are showing that it does confirm the authentication token on launch but then finds the token expired later on when running a process.
Do you have any anti-virus apps running, browser extensions or using a VPN that could be causing interference when the app is running a check on export?
Going to send the logs to the team for investigation to see why the token is showing as expired after being verified on launch.
I use and have always used a VPN. I did just change it from Florida to New Jersey as access was horrible on the Florida side. That’s the only change I made before this started happening, but it came through ok yesterday with the NJ IP.
When I launched the program I got a screen requiring me to authenticate with the website, which I did. The problem went away. It appeared as if the account was reset?
I wonder they do re-authenticate while encodes are running, since authentication is already done every time the program starts.
This is what I suggested above (with the “manual log out”). If you did that correctly
you’d have gotten the “Activate” window at the next start leading you to the authentication web page.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
