- #NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN HOW TO#
- #NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN LICENSE KEY#
- #NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN VERIFICATION#
- #NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN SOFTWARE#
- #NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN CODE#
There are two ways you can restrict the number of machines that can use a license: If you would like to remove some of the machines codes, you can click on the yellow button next to each license and remove the machine codes in from the list. That’s because the platform does not know which machine codes should work and which should not. 5, all of the activated machines will still work. If you decrease this value to something less than 10, eg.
#NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN CODE#
Let’s say you had maximum number of machines set to 10 and one customer has used up the machine code quota, i.e. As a solution, please check the MaxNumberOfMachines field, ensuring it is not 0, before calling Helpers.IsOnRightMachine(). Note, Helpers.IsOnRightMachine() will return false if no machine code is registered with the license, which will be the case if maximum number of machines is set to 0.
#NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN SOFTWARE#
It means users will be able to run the software on any number of machines. machine codes will not be added to the license. Setting maximum number of machines to zero turns this feature off, i.e. There are two special cases that is important to keep in mind: Setting to zero When the limit is reached, no more machine codes will be added. Maximum number of machines is a way to specify how many unique machine codes can be added to a certain license (using the Activate method). Our plan is to integrate this into all client APIs so that you can have most of the license logic set up in the dashboard. Recently, we have added support in our Web API that takes into account the feature definitions and adjusts the response sent to the client. if F1 stands for a time-limited license and it’s not enabled for a certain license, there won’t be an option to prolong it).
#NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN HOW TO#
They can be used as a way to help you to keep track of what each feature flag means and they also help our platform understand how to display a certain license in a meaningful way (eg. You may noticed that you can edit feature definitions in each product. If you do not know when your customers will activate the license for the first time but you still want them to use it for a set number of days, you can enable trial activation. However, once it has been activated, it will be blocked after the new expiration date (assuming that the license is marked as time-limited). This way, you can pre-generate the licenses and ensure that your customer can still activate them, even when the expiration date has passed. For example, if you have created a license with start countdown upon activation=true and MaxNoOfMachines=1, it will not be blocked if it has not been activated. if start countdown upon activation (aka trial activation) is enabled, provided that the maximum number of activations has not been reached.
#NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN LICENSE KEY#
if the license key has a data object with the name cryptolens_stripesubscriptionitemid, since these licenses are managed by Stripe through the recurring billing module.Note: the following licenses will not be blocked: Expired licenses will be blocked within an hour. In order to ensure that licenses stop working after that they have expired, you can select “Block Expired Licenses” when editing feature names. If you plan to support both time-limited and time-unlimited licenses, you can use one of the feature flags as a way to distinguish this. A way to do this is to call HasNotExpired (depending on the library) or simply check the Expire field. This may feel a bit counter-intuitive and we are continuously working on improving the APIs to make this more trivial.įor now, if you see that a code-example contains a call to the activate method (which all examples do at the moment), it means that you need to check the expiration date even if you get a successful result.
#NOMACHINE AUTHENTICATION FAILED PLEASE TRY AGAIN VERIFICATION#
For example, all code snippets provided in the key verification tutorial assume that a license is time-unlimited. It turns out that expiration date will not affect the validity of a license by default. The question is, how can we create licenses that never expires? On the product page, every license has a field called Expires. When you create a new license, you are asked to set when it should expire. Protecting RSA Public Key and Access Tokens.Definition of an end user / machine code.The FAQ is a work in progress and is continuously updated based on questions we receive by mail.
0 kommentar(er)
