hi, <@498057949541826571> We encountered this erro...
# support-questions-legacy
p
hi, @rp_st We encountered this error when we tried to log in. But we did not make any changes to supertokens that would affect this. why could this be? SuperTokens core threw an error for a request to path: '/public/recipe/signin' with status code: 403 and message: Email password login not enabled for tenant.
r
hey @phenomenal_moose_56739 are you using multi tenancy feature?
z
Yes we are using
r
ok, so when you created the tenant, which login methods did you enable for it?
p
emailpassword login method
I get this error when I try to enter the license key.
AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (, public, public)
r
can you show me the full error stack please?
and im not sure how the previous error is related to the license key entering error. Could you please clarify what steps you are doing?
@sattvikc can helpp here.
p
There was no problem working with my teammates today. Even though we did not make any changes to the supertokens, we received this error when logging in. "SuperTokens core threw an error for a request to path: '/public/recipe/signin' with status code: 403 and message: Email password login not enabled for tenant." Then, we manually deleted all tenants in the dev environment from the database. then, We saw a license key error and when we tried to enter the license key with curl, we also received this error. "AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (, public, public)"
r
Right. When you say you manually deleted the tenants, u also deleted the public tenant? That’s not a good idea since that should alway be there
You should restart the core. Maybe that will fix the inconsistent db state
As per the previous error, you should check if you had enabled email password login for that tenant.
20 Views