-
-
Notifications
You must be signed in to change notification settings - Fork 567
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
Shows warning that user count exceeds license with three internal users on self hosted instance #9051
Comments
Quick update: The warning has gone away. I still have not changed anything. |
I've been running Authentik a few months now, and I'm getting this error. I couldn't log in to the admin interface without generating a recovery token. I've only got 3 users (akadmin, an outpost user, and my user). Not sure what I need to change. I'm running it with docker-compose. The image I'm using is as follows - perhaps this is an enterprise image? I couldn't find any reference to a different image for open source users:
|
@DavidFuchs could you run from django.core.cache import cache
from authentik.enterprise.license import LicenseKey, CACHE_KEY_ENTERPRISE_LICENSE
from authentik.enterprise.models import License
print(LicenseKey.get_total().summary())
print(cache.get(CACHE_KEY_ENTERPRISE_LICENSE))
print(License.objects.all().count()) |
Absolutely, here are the results:
|
Well hold on, now the error is gone. And I'm able to log in again. /confused |
@BeryJu I have the same issue except my warning banner is red. I cant create applications.
I read somewhere that having multiple Brands is an enterprise feature, i have created my own Brand and deleted the Default Brand, could that be the issue? if so, how do i fix it? |
@thefeli73 having multiple brands is not an enterprise feature; which version are you running? There was a bug with this in 2024.2.1 so make sure you're on 2024.2.2 |
@BeryJu That was indeed the issue! Thank you! |
i'm having the same issue and i just updated to 2024.2.2.
any idea how i could fix it? i'm also not able to login |
I redeployed the docker containers and this solved my issue. No idea what was the problem. |
The same issue for me, worked for a ~month and now this. Updated from |
What can I do, to fix same problem? |
What did you do to fix it? |
We have the exact same issue. It predicted 100+ users when we had 5 users. Then yesterday it predicted "0 users". Now we can't log in any more. |
Now fixed for us. We updated authentik to the last version. |
It works again for me.
My guess is that the logging of the license refreshes some kind of cache in the background and/or triggers something internally to fix itself. The update to the latest version alone + restart didn't fix it. Only after doing the logging + another restart fixed it. |
We have the same issue. However, neither updating the version nor adding |
@Krishnacore Did you do the exact sequence of things I posted? Including restarting everything a couple times? :) |
I also had this problem even after updating to 2024.2.2 and doing all steps above. I assumed my instance was in a bad state so in the shell I took a guess and set the warnings and read only back to false in the cache key with these additional commands to the ones above. import datetime
cache.set(CACHE_KEY_ENTERPRISE_LICENSE, {'internal_users': 0, 'external_users': 0, 'valid': False, 'show_admin_warning': False, 'show_user_warning': False, 'read_only': False, 'latest_valid': datetime.datetime(1970, 1, 1, 0, 0), 'has_license': False}) That seemed to fix it and my normal user could log in again. Restarting the containers and the error remains gone. |
Thanks for this, the above method was also not working for me either, but your solution resolved the issue. |
setting The issue was caused by a bug in 2024.2.1 which was fixed in 2024.2.2, but incorrect values could be cached and thus the warning banner/read only mode would wrongly be enabled. The workaround is to remove the faulty cache item ( |
I also ran into this issue which prevented me from accessing my self-hosted authentik instance containing only two users. Any attempt to login raised a @BeryJu's comment is the fix, but it's missing a couple of details. I'm sharing what I had to do for reference. I self-host authentik with docker-compose, so I first upgraded the image to the latest version, then I ran the following:
After this I restarted authentik and everything worked as expected. Since this is deleting a cache entry I doubt restarting is necessary but I did so before testing if simply deleting the cache entry worked. Either way I'm glad my authentik instance is back to working—I love this piece of software! |
Describe the bug
The dashboard has started showing a warning that "The current user count has exceeded the configured licenses". I'm self hosting and can find no documentation that there is a limit to the number of users I can have. I also find it unlikely that that limit would be <= 3.
To Reproduce
Log in as akadmin
Warning shows
Expected behavior
Dashboard with no warning should show
Screenshots
Logs
authentik.log
Version and Deployment (please complete the following information):
Additional context
Running on synology nas, error just popped up without any changes to configuration.
Docker compose definition:
The text was updated successfully, but these errors were encountered: