Skip to content
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

[BUG] Error while checking license #2609

Closed
1 of 2 tasks
mo6zes opened this issue May 13, 2024 · 2 comments · Fixed by #2661
Closed
1 of 2 tasks

[BUG] Error while checking license #2609

mo6zes opened this issue May 13, 2024 · 2 comments · Fixed by #2661
Assignees
Labels
bug Something isn't working

Comments

@mo6zes
Copy link

mo6zes commented May 13, 2024

Issue Summary

After a certain period of time after boot on my self-hosted instance, I see the error "Error: Error while checking license" popping up. This results in all forms being unusable, see screenshot:

Scherm­afbeelding 2024-05-13 om 10 22 08

Steps to Reproduce

  1. Self-host instance (with enterprise license I think)
  2. Wait some hours

Expected behavior

License should work

Other information

No response

Screenshots

Scherm­afbeelding 2024-05-13 om 10 32 04

Environment

  • Formbricks Cloud (app.formbricks.com)
  • Self-hosted Formbricks

Desktop (please complete the following information)

- OS: mac
- Node: chrome
- npm: -
@mo6zes mo6zes added the bug Something isn't working label May 13, 2024
@mattinannt
Copy link
Member

@mo6zes Thanks for creating an issue. We will look into it right now and see what the issue is.
Did you provide a Formbricks license key inside your environment variables? And does your instance have internet access?

@mo6zes
Copy link
Author

mo6zes commented May 13, 2024

Yes to both. And this problem started occurring after the 2.0 update.

I have this env variable:

ENTERPRISE_LICENSE_KEY=*****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants