Open yesbhautik opened 9 months ago
I'm getting the same error , found any solutions ?
Have you migrated your supabase database?
I ran into this problem running locally and it turned out there was some kind of port conflict with docker. To fix it I ran supabase stop
, restarted my computer, then ran supabase start
I am using Local Method in my Ubuntu Server [because I dont wanna use vercel and supabase cloud]
I'm getting the same error , found any solutions ?
I got the solution.
I have done as below & it works...
1 cloned repo
2 npm i
3 npm install supabase --save-dev
4 nano .env OR set values to env variable if you are using any panel for more security with [SUPABASE_ACCESS_TOKEN (supabase account api), NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, EMAIL_WHITELIST]
5 modified "supabase/migrations/20240108234540_setup.sql"
6 supabase link --project-ref
[if you are in any panel and hard to modify the code or unable to access the terminal enough permission then you can perfrom step 1 to 7 at any device, doesnt matter that device is local or online then mention repo URL in your panel just set env variable and you good to go smoothly]
BUT BUT BUT, I am getting one another issue. I have white listed one domain because I was getting "Email [email-id] is not allowed to sign up." But i didn't worked for me. I have to white whole email address to get signed up. What if I want to make site open for all with one specified domain or all domains?
ENV:
ERROR:
I am getting the same error running locally. I've tried restarting my PC, but it won't work :(
restarting my PC
RESTART WILL NOT WORK 🤣, In cloud getting same error, then error inside the script.
Same issue and local app wasn't working, once stopped and restarted supabase the error messages still appeared in the terminal but the app seams to work fine for now
Same issue and local app wasn't working, once stopped and restarted supabase the error messages still appeared in the terminal but the app seams to work fine for now
I have give solution for it brother. New issue is sign up restrictions.
@yesbhautik the second issue you ran into after getting past that first one is due to a bug in the sign up logic. The issue stems from setting both EMAIL_DOMAIN_WHITELIST
and EMAIL_WHITELIST
at the same time.
I just created a pr (#1406 ) with a fix, but in the meantime you should be able to get things up and running by only setting one of those whitelist environment variables at a time.
only setting one of those whitelist environment variables a
Okay let me try with it
@yesbhautik the second issue you ran into after getting past that first one is due to a bug in the sign up logic. The issue stems from setting both
EMAIL_DOMAIN_WHITELIST
andEMAIL_WHITELIST
at the same time.I just created a pr (#1406 ) with a fix, but in the meantime you should be able to get things up and running by only setting one of those whitelist environment variables at a time.
unfortunately, not worked for me 😢 .
@yesbhautik hmm same error as before? what does your .env file look like now?
yes same error. here is my current environment var.
@yesbhautik i can't reproduce the error when i only have EMAIL_DOMAIN_WHITELIST
set in my .env.local
file
i'm running the app locally with npm run chat
in a console window though and it looks like you're using easypanel to host the app. i suppose it's possible there's some extra setup needed to make it work with easypanel, but i'm not familiar enough with easypanel to say one way or the other. Maybe try switching that "Create .env file" toggle button at the bottom of your screenshot?
sorry, wish i could be more help, good luck!
easypanel
Everything working superb, in this panel. And if evn values not getting by script then database will not connect. So tuggle on .env not make sence. Btw, your PR is not approved yet so maybe your concept will not work
sign up restrictions issue resolved,
if you don't want to restrict anything then, just create variable for it and dont put any value. but if dont create any variable then it will show the restrictions ERROR.
just keep it blank as below...
Ok guys it is no fun any longer. Why did you introduced a login but whatever I do set everything to true, No email login is allowed. Nor can I ever use any longer the chatbot ui, as I get stuck at Login screen, please remove it!
Ok guys it is no fun any longer. Why did you introduced a login but whatever I do set everything to true, No email login is allowed. Nor can I ever use any longer the chatbot ui, as I get stuck at Login screen, please remove it!
owner and contributer not focusing on basic stuffs [not limited to login, other many basic things which is more important then adding new features].
Ok guys it is no fun any longer. Why did you introduced a login but whatever I do set everything to true, No email login is allowed. Nor can I ever use any longer the chatbot ui, as I get stuck at Login screen, please remove it!
owner and contributer not focusing on basic stuffs [not limited to login, other many basic things which is more important then adding new features].
I know @yesbhautik I do not blame here, it is just that I lost all data due to this story of Login no Login, each update some new bugs are coming from the Login feature that is not of use for many in offline mode! At least that one can switch it off/skip it and if not that it is fixed. I thought, if something it is introduced it goes through bug fixing phases before release. At least how I manage things in my team. The login issue is not the first one of its kind (I know how picky these phases are, learned a lot of these lessons the hard way)
Again not being upset with anyone it is just a pain that such a beautiful development is not of use due to the Login blocking users to use it. A visually "small" thing blocks the main use! (PS: Login and Credentials are never a small thing ;) ) It appears just from UX :)
So would be good if the devs could focus on it, as I used it for work and development heavily! Thx in advance
I needed to make it work after more than a week of painful only having ChatGPT on OpenAI Here are the steps I used. --> Please investigate developers if this is the way to go and if not please take my steps to make a tutorial for others. Thx.
Adjust Supabase Configuration:
Verify Email in Supabase Studio:
Reset Password via Email:
I am coming from https://github.com/mckaywrigley/chatbot-ui/issues/1424
I can just say that after trying the options explained above, I still did not manage to get it working on Mac (Intel CPU). Therefore I will revert to the legacy version of chatbot-ui for now.
Thank you for your work!
I'm getting the same error , found any solutions ?
I got the solution.
I have done as below & it works...
1 cloned repo 2 npm i 3 npm install supabase --save-dev 4 nano .env OR set values to env variable if you are using any panel for more security with [SUPABASE_ACCESS_TOKEN (supabase account api), NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, EMAIL_WHITELIST] 5 modified "supabase/migrations/20240108234540_setup.sql" 6 supabase link --project-ref [no need to enter any password] 7 supabase db push [need to enter password which you have set during database creation on supabase cloud] 8 npm run dev -- DONE --
[if you are in any panel and hard to modify the code or unable to access the terminal enough permission then you can perfrom step 1 to 7 at any device, doesnt matter that device is local or online then mention repo URL in your panel just set env variable and you good to go smoothly]
Thank-you!!! I did a hosted deployment fine, but locally on Ubuntu was stuck, this fixed it for me.
Ok guys it is no fun any longer. Why did you introduced a login but whatever I do set everything to true, No email login is allowed. Nor can I ever use any longer the chatbot ui, as I get stuck at Login screen, please remove it!
owner and contributer not focusing on basic stuffs [not limited to login, other many basic things which is more important then adding new features].
I know @yesbhautik I do not blame here, it is just that I lost all data due to this story of Login no Login, each update some new bugs are coming from the Login feature that is not of use for many in offline mode! At least that one can switch it off/skip it and if not that it is fixed. I thought, if something it is introduced it goes through bug fixing phases before release. At least how I manage things in my team. The login issue is not the first one of its kind (I know how picky these phases are, learned a lot of these lessons the hard way)
Again not being upset with anyone it is just a pain that such a beautiful development is not of use due to the Login blocking users to use it. A visually "small" thing blocks the main use! (PS: Login and Credentials are never a small thing ;) ) It appears just from UX :)
So would be good if the devs could focus on it, as I used it for work and development heavily! Thx in advance
my solution will work, for sure. you can use your old supabase DB to restore your data
I don't get what I am doing wrong. I tried to follow the steps outlined as the fix and i still cannot create a user from the backend and I get errors like made from the front end. Before I go into my setup and exactly what I see, is there something basic I should try first?
I changed the NEXT_PUBLIC_SUPABASE_URL to my local ip. Works now.
Could someone maybe write a fix more clearly? I have tried it few times and still does not work. I am using MacBook pro Sonoma 2,3 GHz Quad-Core Intel Core i7.
Exact same issues with @jaimejim . I do not get why related issues are closed. They seem to be related to migration issues; something fundamentally wrong. Related issues are closed without explanation. The only one I found with an explanation is this by @yesbhautik , which does not work: https://github.com/mckaywrigley/chatbot-ui/issues/1427#issuecomment-1937798722
That being said, thank you very much @yesbhautik and @mckaywrigley for all your hard work! I appreciate how incredible it is that awesome people like you are putting out their hard work and trying to support others as they try to build on work! All the best and have a great week.
Sorry for late reply I am outside of my desk with my family from last few days, @Mahogany95 what issue you are facing? Please explain it so i can help. Also, if you need urgent/personal help please ping me on telegram @yesbhautik or just schedule free meet with me on TopMate
I changed the NEXT_PUBLIC_SUPABASE_URL to my local ip. Works now.
it works
如何取消不用邮箱登录呢?
Logs:
Error: