Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

License check affect page load (long load, error) in airtight environments #6791

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

Closed
avengerweb opened this issue Mar 20, 2025 · 3 comments
Closed

Comments

@avengerweb
Copy link

  • Laravel Version: 10.x
  • Nova Version: 5.x
  • PHP Version: 8.3
  • Database Driver & Version: PostgreSQL 16
  • Operating System and Version: Docker/Ubuntu 22
  • Browser type and version: Chrome

Description:

Our Laravel application is deployed on an enterprise private cloud with strict internet access (no internet) using backed Docker images.

Sometimes, the Nova page takes a significant amount of time to load (or even error as we have tight load time limits on some of our projects), and the logs show that it is trying to check the license.

At the end, a red “unregistered” mark appears on the navigation bar, which confuses users since we do have a license (although the delayed page loading is a more critical issue).

There is already a discussion on this topic:
#5790

It would be great if license could be checked during build time (ex. composer install or artisan command) or at least license check to use "queue".

Detailed steps to reproduce the issue on a fresh Nova installation:

  1. On any nova laravel project
  2. Disconnect from wife
  3. clean cache
  4. try to open /nova
@avengerweb
Copy link
Author

Any updates on this one?

This comment has been minimized.

@stale stale bot added the stale label Apr 26, 2025
@crynobone crynobone removed the blocked label Apr 26, 2025
@stale stale bot removed the stale label Apr 26, 2025

This comment has been minimized.

@stale stale bot added the stale label May 1, 2025
@crynobone crynobone removed the stale label May 1, 2025
@laravel laravel locked and limited conversation to collaborators May 1, 2025
@crynobone crynobone converted this issue into discussion #6838 May 1, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants