-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Table 'tabby.app_user' doesn't exist" #119
Comments
I ran into the same issue. When running the docker-compose file I noticed that the tabby-web container was not able to connect to the DB server. I don't think the DB server was created or even running when the tabby web server went through its setup. The fix I came up with was to create a docker compose for the DB server and remove that section from the docker-compose file for the tabby-web server. I the started up the DB server and then the web server. my setup looks something like this docker
Start order
Here are the sanitized versions of the docker-compose.yml files. tabby-db docker-compose.yml
tabby-web docker-compose.yml
tabby-connection-gateway docker-compose.yml
Having done all that to get the containers up and going I still cant make it work. I think my issue is connecting tabby-web to the tabby-connection-gateway when setting up the Connection Gateway I have tried ws://IP:9000 < invalid - An insecure WebSocket connection may not be initiated from a page loaded over HTTPS I don't see anything in the tabby-connection-gateway or tabby-web logs using " docker logs --follow " |
Well I give up. I blew away the directories and started over. I discovered if you run the tabby-web docker-compose.yml the stop it, then run it again the DB issue gets sorted out. But now the oauth isn't working at all. The call back url, secrets, and client ID have not changed it just sends me to a github 404 page once I authenticate. |
Hello, change services order: |
I just encountered and resolved this issue. By observing the first line of output from the tabby container, one can notice this error:
It is evident that the issue was caused by the
to
the issue can be resolved, and one can successfully access the webpage. However, upon further consideration, it becomes apparent that this error will occur in the webpage as long as the tabby container does not successfully connect to the db. Therefore, the reason you encountered this error might be different from mine. You can try the above solution or carefully analyze the log of the tabby container to find the real cause of the error. |
@Satone7 |
This should be succested as PR |
Use the default Docker Compose.yml file without any modifications
The text was updated successfully, but these errors were encountered: