nova 4 says "unregistered" in red

[legodion]

• Laravel Version: 9
• Nova Version: 4

Description:

nova is saying "unregistered" in red beside the logo on localhost

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

i installed nova, entered my credentials for composer, and everything installed just fine

i have an unlimited license key, yet nova says "unregistered" in red beside logo

i tried entering my license key in the nova config file and it still says "unregistered" in red

how do i fix this?

[crynobone]

You probably has cache based on before inputing the value. Should be cleared after an hour max.

[imClement]

Hi.

In our case didn't cleared after 1 day.

1 domain license with the domain added to the nova.laravel.com dashboard

[crynobone]

@imBuidler can you email to nova@laravel.com with your Nova account e-mail address so we can double-check with our system, thank you.

[nathan-io]

I'm seeing this both on my local and on a production server. Using an "unlimited" license key in both cases.

i tried entering my license key in the nova config file and it still says "unregistered" in red

I didn't realize this config key existed, it's not mentioned in the upgrade guide. I only saw it after looking at vendor/laravel/nova/config.php.

Adding a note about this to the upgrade guide will likely prevent some confusion.

After entering the value and running optimize:clear and nova:publish on my local, the "Unregistered" disappeared. I haven't tried on the production server yet.

The comment in config says:

On non-local domains, Nova will verify that the Nova installation has a valid license associated with the application's active domain.

This may need to be updated to reflect that this behavior also occurs on local domains.

---

This is a separate issue but for some reason, on the production server, Composer successfully upgraded from Nova 3.31 to Nova 4.0 when our auth.json still had a v3 key. However on my local, using the same key, the upgrade operation failed with "The license associated with this API key is not eligible for updates!"

[nathan-io]

After entering the value and running optimize:clear and nova:publish on my local, the "Unregistered" disappeared. I haven't tried on the production server yet.

Still seeing "Unregistered" after performing these steps on the production server, even after clearing cache and doing a hard refresh.

[gcg]

Putting the licence key field 'license_key' => env('NOVA_LICENSE_KEY'), to nova config file (config/nova.php) does the trick.

Since upgrade guide has no mention for such a field, it was a fun adventure to figure out why it's not working tho :)

[davidhemphill]

This is mentioned in the documentation: https://nova.laravel.com/docs/4.0/installation.html#registering-a-nova-license-key

[gcg]

This is for INSTALLING, we should mention this in the UPGRADING page as well since existing nova users won't click on install.

[kgp43]

This is mentioned in the documentation: https://nova.laravel.com/docs/4.0/installation.html#registering-a-nova-license-key

Seems this been removed from the documentation?

[crynobone]

Still there, try doing hard refresh to remove browser caching:

https://github.com/laravel/nova-docs/blob/master/4.0/installation.md#registering-a-nova-license-key

[wdelfuego]

Not requiring guzzle in your project’s composer.json causes this to occur as well, since the license validity check depends on it.

I’d expect guzzle to be included in Nova’s own requirements because of that dependency, I’m not sure why it isn’t. Feels like poor man’s DRM because pirated users can simply return true from the check method while paying users are confronted with red screaming labels in every screen.

---

Update: Nova team has indicated that Guzzle is a peer dependency of Laravel and that therefore neither laravel/framework nor laravel/nova have Guzzle listed as a dependency, so if if it's not there yet you'll need to add guzzlehttp/guzzle manually to your project's composer.json or you'll get the persistent Unregistered banner under any circumstance.

Update2: so to try this fix:

• require guzzlehttp/guzzle in your project
• run composer update
• run php artisan optimize:clear to avoid caching issues

[davidhemphill]

Nova doesn't directly use Guzzle anyways. It uses the in-built Laravel Http client which uses Guzzle. Nova's dependency is on Laravel itself and assumes the user hasn't removed the things Laravel needs. 😉

If we specified a version of Guzzle to be used with Nova, this would cause installation issues with Laravel projects installing the Guzzle peer dependency. This peer dependency inside Laravel has been around for a long time for this exact reason.

As an aside: license keys provide a lot of helpful insight into where/how Nova licenses are used. There's more going on than a little bit of red text to annoy users who forget to put their license key in. 😅

[nathan-io]

The composer.json you linked comes from the laravel/laravel skeleton project and does indeed include the guzzlehttp/guzzle dependency since 7.0

That skeleton is what you get when you install Laravel, so they're assuming that your composer.json is going to start out like that.

The approach you described (requiring laravel/framework, Nova, and Tinker directly) isn't something I'm familiar with or would recommend.

[wdelfuego]

@davidhemphill Thanks for the addition!

@nathan-io Including them directly is what the skeleton framework does so it seems to be how it is supposed to be done. Your own composer.json probably does it too. I was misinterpreting the laravel/laravel package as a library to include when it’s just an application skeleton, a starting point for new laravel apps.

[clementmas]

Is Nova making a Guzzle HTTP request on every page load to check the licence? If so, isn't it a performance issue?

[davidhemphill]

It makes a request every hour (if someone uses the admin). The request result is cached.

[Sotiris-k]

I've required guzzle, optimize cleared and the UNREGISTERED indication is still there.

[lukebouch]

I'm having the same issue.

[clementmas]

People still having the issue (in production), did you add your URL to the "Production URLs" field of your Nova v4 licence?

Nova maintainers: is this field required even if we have an Unlimited licence?

[davidhemphill]

Yes, you need to input the sites that will be used for license verification to work.

[Sotiris-k]

Is it supposed to say unregistered on .test sites? Because it does to me.

[RhysLees]

Is it supposed to say unregistered on .test sites? Because it does to me.

No, if you put your licence key for nova in your .env then it won't say u registered.

You need to clear cache after

[moroneyio]

Yes, you need to input the sites that will be used for license verification to work.

Have you provided a wildcard domain license for unlimited license holders for saas projects (I've tested using *.blahblah.com doesnt work in a saas setup) ? or atleast an API to automate adding domains to a unlimited license ?

Without veering off topic and having a degree of trust you will address these issues i have to wonder why Nova 4 had to be so anti branding

[davidhemphill]

Have you provided a wildcard domain license for unlimited license holders for saas projects (I've tested using *.blahblah.com doesnt work in a saas setup) ? or atleast an API to automate adding domains to a unlimited license ?

@itsmejoshua The domain list already supports wildcards.

[wdelfuego]

A comment I posted on this discussion earlier today was silently removed, presumably by @davidhemphill. I wasn't informed about that removal nor do I see any trace of it here, so I'll have to guess as to what was the reason. I assume it was because of a line of code I shared that was meant to help licensed users not be bothered by the Unregistered message. I figured it'd be an acceptable workaround for the people running into this issue but I won't share it again just in case that that line was the reason for removing my comment. I'm surprised by the fact that comments are being removed here without a trace and without a notice to the author; I'd be happy to have removed the line myself if I had known that that was going to be an issue.

In the same comment I also shared my opinion about the Unregistered label itself which I think is a valid opinion to share on a Discussion like this so I will repeat it here: I understand the needs for digital rights management, but as always, users who play by the book pay the price for something that unlicensed users aren't bothered by. I think it'd be in the interest of both the Nova licensees and the Nova maintainers to get rid of the message in the front-end (not the license validity checks themselves) so licensed users aren't bothered by them and unlicensed users aren't informed about the fact that Nova can see that they're using an unlicensed version.

[JshGrn]

A comment I posted on this discussion earlier today was silently removed, presumably by @davidhemphill. I wasn't informed about that removal nor do I see any trace of it here, so I'll have to guess as to what was the reason. I assume it was because of a line of code I shared that was meant to help licensed users not be bothered by the Unregistered message. I figured it'd be an acceptable workaround for the people running into this issue but I won't share it again just in case that that line was the reason for removing my comment. I'm surprised by the fact that comments are being removed here without a trace and without a notice to the author; I'd be happy to have removed the line myself if I had known that that was going to be an issue.

In the same comment I also shared my opinion about the Unregistered label itself which I think is a valid opinion to share on a Discussion like this so I will repeat it here: I understand the needs for digital rights management, but as always, users who play by the book pay the price for something that unlicensed users aren't bothered by. I think it'd be in the interest of both the Nova licensees and the Nova maintainers to get rid of the message in the front-end (not the license validity checks themselves) so licensed users aren't bothered by them and unlicensed users aren't informed about the fact that Nova can see that they're using an unlicensed version.

The nulled versions anyway have just removed it so it really doesn't effect those either, only the people who pay.

[nrueckmann]

For me it's still showing the "unregistered" line. Even on local environment. Nova 4.2.4, fresh installation, NOVA_LICENCE_KEY before installing nova.

[Sotiris-k]

You have a typo, it's license, not licence ;)

[nrueckmann]

Jesus Christ .. mea culpa.

[nrueckmann]

And thanks, of course.

[NowakAdmin]

I had same problem, I've found a solution for me:
php artisan nova:check-license
Response should be:
Your license key is valid and correctly configured! Thank you for being a Nova customer. 🚀
That proove that settings are ok (this will tell in Your case about error with no valid key [typo]).
Then clear cache:
php artisan cache:clear
(I had to do it as sudo user: sudo php artisan cache:clear)
Response should be:
Application cache cleared successfully.

Above fixed issue in my case (it was caching)

[almirhodzic]

For me the problem was the space between NOVA_LICENSE_KEY =KEY in my .env file!

[davidhemphill]

Make sure to run php artisan nova:check-license after adding your license key to your environment/config file. This will check your license key installation and clear/set the cache value. This should fix the issue.

[s-fog]

still having same issue after all of this steps
docker exec -it dog_php_production php artisan cache:clear
INFO Application cache cleared successfully.
docker exec -it dog_php_production php artisan nova:check-license
Your license key is valid and correctly configured! Thank you for being a Nova customer. 🚀

Even command told to me that iam verified

[Hannes-Kruger]

One of these two should do it:

php artisan nova:check-license

php artisan cache:forget nova_valid_license_key

[s-fog]

Nothing is working (( In production i have this stupid "unregistered". All keys are correct. Tried everything in this discussion.

[s-fog]

No. Do i need to do it?) Never did it, build a lot of projects

[almirhodzic]

It helped me to solve that issue

[s-fog]

Hm. Nothing helps. This artisan command php artisan cache:forget nova_valid_license_key. Any of commands that introduce here. Helps only this code. Dont know why artisan command didnt work. Thanks for help.

Cache::forget('nova_valid_license_key');
var_dump(Cache::get('nova_valid_license_key'));
var_dump(Nova::checkLicenseValidity());

[s-fog]

Very strange behavior. When i did previous code, everything works fine. But when i log in after day, there is unregistered again.

public static function checkLicenseValidity()
    {
        return Cache::remember('nova_valid_license_key', 3600, function () {
            return rescue(function () {
                return static::checkLicense()->status() == 204;
            }, false);
        });
}

For some reason, checkLicense fails again... Somebody has any suggestions? I didnt deploy any edits.

[s-fog]

Fix it. In setting was domain, but nova is on subdomain.

[hitanshi2996]

Finally I found the Issue,
Its in the HTTP call error of
cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nova.laravel.com/api/license-check

you just have to do the changes in PHP.ini file like below

in your case it can be diff

after fixing this HTTP SSL issue dont forget to do

php artisan cache:forget nova_valid_license_key