I have tried various methods like clearing cache/cookies, setting token in agent config, setting uuid in env variable. I am not running a docker container, so I imagine /home/username/.tabby/ee/sqlitedb is persistent storage. However, I still can't log into the web server after restart. What could be the issue?
Stephen
Asked on Jan 30, 2024
There could be several reasons why you are unable to log into the web server after a service restart. Here are some possible solutions:
Double-check the configuration: Make sure that the token is correctly set in the agent config and the UUID is properly set in the environment variable.
Verify the persistence of user information: If you are not running a Docker container, ensure that the /home/username/.tabby/ee/sqlitedb directory is indeed persistent storage.
Check for any console or network errors: Use tools like the Jam.dev Chrome extension to record the console and network activity during the login process. This can help identify any errors or issues that may be preventing login.
Clear cache and cookies: Sometimes, clearing cache and cookies can resolve login issues. Try clearing everything and then attempt to log in again.
Verify the correctness of copied information: If you are copying any information, such as the token or UUID, double-check that you have copied it correctly.
If none of these solutions work, it may be worth reaching out to the support team for further assistance.
