Activation Code Not Accepted

[DarveyLavender]

I received and entered the activation code on Linux and MacOS but the entering of the code did not change the Buy or Continue with Trial.

[dkapanidis]

Hi

Normally reports of invalid licenses are due to the following potential cases:

• Keys are finished with two "==" characters, make sure when copying the text they are also included.
• Some mail clients have been reported to split license keys with end-of-line. Make sure there are no empty lines between characters.
• In a weird situation a mail client added a "!" character in the license keys. The license keys are base64 of the signed license. They do not include characters such as "!". You can test the keys from your side by doing "echo $LICENSE_KEY | base64 -D".

Hope this helps, please confirm if everything is ok here.

[DarveyLavender]

Thanks for the quick response. Noting that the license ended in == helped. I use Outlook and the in the email was truncated. I had to open the email in a browser.

You may close this case.

Darvey

---

From: Dimitris Kapanidis @.> Sent: December 19, 2021 6:10 PM To: harbur/kubernetic @.> Cc: DarveyLavender @.>; Author @.> Subject: Re: [harbur/kubernetic] Activation Code Not Accepted (Issue #330)

Hi

Normally reports of invalid licenses are due to the following potential cases:

• Keys are finished with two "==" characters, make sure when copying the text they are also included.
• Some mail clients have been reported to split license keys with end-of-line. Make sure there are no empty lines between characters.
• In a weird situation a mail client added a "!" character in the license keys. The license keys are base64 of the signed license. They do not include characters such as "!". You can test the keys from your side by doing "echo $LICENSE_KEY | base64 -D".

Hope this helps, please confirm if everything is ok here.

— Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fharbur%2Fkubernetic%2Fissues%2F330%23issuecomment-997479239&data=04%7C01%7C%7Cf5f0998beeed4e9dd3f208d9c344cd58%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637755522531452609%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=hF5U7eg0ybCW8JWFdbJtrRQYlv%2FNJc50WjM55o0HNrk%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMGA5DIZH6N5M4POYAF7V5TURZQ7XANCNFSM5KMMN4IQ&data=04%7C01%7C%7Cf5f0998beeed4e9dd3f208d9c344cd58%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637755522531462578%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=d%2FolsZkQm%2FaWY178D8bUxlnYLTwHXU5xCCxcuQICHjA%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7Cf5f0998beeed4e9dd3f208d9c344cd58%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637755522531472530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=lRJtHEHMmJuD5iSSoQTCBICYFVZ8pu4KI%2BLZM4jIzJE%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7Cf5f0998beeed4e9dd3f208d9c344cd58%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637755522531472530%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=YUeVxZbPn77haqEDDmrfi8QMw8MU84qehPyAcSZhCO0%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>