-
Notifications
You must be signed in to change notification settings - Fork 8
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
Initial login/setup for TBA in docker does not work #710
Comments
Further information: I am running an NPM proxy frontend and have tried access through both the proxy and direct to the 8095 published port but the behaviour is the same. Access to port 5173 shows a JSON console with the following: Health OK |
Hello, thank you for the report! We do have some basic username/password authentication support (known as password auth mode), however we recently made significant changes to our login flow, so I expect something on the frontend is broken. There's some additional blockers for self-hosting needs. Password auth mode does not have a way to create a user, and the initial setup wizard relies on connecting with Google Calendar (which requires a Google Oauth app.) We're already planning on adding CalDav support to the setup wizard, so I'll block off time to ensure that the login flow works with password auth mode, have it create a user on first-login, and add some more documentation for self-hosters. Finally the current docker containers are setup for local development use, I'll have to take a look at our IaC to make sure there isn't some huge issue if someone were to deploy those to a public-facing instance. Thanks again for the report and testing it out though! |
Seriously? |
Hi Melissa Thanks v much for the reply. Can you clarify a few items:
Really interest in TBA so looking forward to a working solution, and happy to be a guinea pig for testing. I tried CalCom but was not overly impressed ... Regards, Robby |
Hey there, Password auth should be set by default. In production we use Mozilla Accounts as an identity provider (which frees us from having to mange user accounts to a certain extent 🙂) The problem right now is there may be a bug in the frontend login code that I have to look at and fix. Once that issue and #120 are fixed you should be able to login to create a new user. Currently the first time user experience (setup wizard) requires a Google Calendar connection (which requires a Google OAuth app from Google). We already have feedback from the beta that some people do not use Google Calendar, so we will be adding CalDav support to the wizard soon. I'm hoping to get this stuff fixed by mid next week, but it may be a bit if other work duties come up. Hope that helps explain the current situation! |
Thanks v much! |
Describe the bug
I've setup TBA in docker on a public host. According to docker logs, everything is running. However I can't get past the login screen, it just sits there without further action.
I can get to the frontend screen and am presented with 2 buttons (login / sign up for beta). Clicking login takes you to another screen (Sign in or create account)) where you can insert an email address and password. After entering the info, and clicking "Continue", the "Continue" button greys out but nothing further appears to happen on the page.
To Reproduce
Expected behaviour
Something should happen after clicking the Continue button like creating the account/starting a setup process/etc.
Actual behaviour
Nothing further happens after clicking Continue
Screenshots
See attached
System (please complete the following information):
Additional context
server = AlmaLinux 9 with DockerCE
Adjustments to std TBA setup
set an alternate outside port for frontend in docker-compose.yml:
ports:
set the password for the mysql tba user in docker-compose.yml
set debug in backend .env
LOG_LEVEL=DEBUG
set db secret and password in backend .env
set mail values in backend .env
set VITE variables in frontend/.env to reflect new frontend port
VITE_BASE_URL=localhost:8095
VITE_SHORT_BASE_URL=http://localhost:8095/user
** Logs **
The logs show no errors even when setting LOG_LEVEL=DEBUG in backend .env
Full docker logs output here attached.
Any assistance would be appreciated.
Regards, Robby
tba-login.txt
The text was updated successfully, but these errors were encountered: