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

Unidoc 3.61.0 gives expired key error when using valid key #564

Open
JoeEdwards-GloveBox opened this issue Aug 19, 2024 · 4 comments
Open

Comments

@JoeEdwards-GloveBox
Copy link

JoeEdwards-GloveBox commented Aug 19, 2024

Sorry if this isn't the normal avenue for addressing such issues, but we have a production issue affecting our customers and so far [email protected] has been unresponsive.

We are a paying customer that seems to have an expired key. We receive the following error when trying to use unidoc: "unable to load unidoc license key: invalid license: The license has already expired.\nYou may need to update the license key to the newest license key for your organization.\nTo find your newest license key, go to https://cloud.unidoc.io and go to the license menu."

Trying to log into our account to fix the issue, via https://cloud.unidoc.io/login, we the following error message is displayed in the UI: Please activate your account first. Inactive User

Our key and account have been working up until a few days ago from what I can tell.

Please let us know how we can correct our account and key. Feel free to reach out directly via my email [email protected] and close the issue if you wish to take this discussion to a different venue.

EDIT:
We have confirmed that we are using a correct key. The issue seems to be limited to when we are using the latest 3.61.0 version. Using the same key with 3.55.0 seems to work fine.

Copy link

Welcome! Thanks for posting your first issue. The way things work here is that while customer issues are prioritized, other issues go into our backlog where they are assessed and fitted into the roadmap when suitable. If you need to get this done, consider buying a license which also enables you to use it in your commercial products. More information can be found on https://unidoc.io/

@JoeEdwards-GloveBox JoeEdwards-GloveBox changed the title Non responsive support Unidoc 3.61.0 gives expired key error when using valid key Aug 26, 2024
@JoeEdwards-GloveBox
Copy link
Author

JoeEdwards-GloveBox commented Aug 26, 2024

I have updated the title and summary of this issue to reflect our latest research into this issue. If you use a valid key/customer name combo, this will fail using unipdf 3.61.0 and will succeed using unipdf 3.55.0.

Here is a little test script which you can use to test the bug:

package bug_test

import (
	"fmt"
	"testing"

	"github.com/unidoc/unipdf/v3/common/license"
)

// Example of an offline perpetual license key.
const offlineLicenseKey = `<LICENSE KEY>`

func init() {
	customerName := `<CUSTOMER NAME>`

	ofk := fmt.Sprintf("-----BEGIN UNIDOC LICENSE KEY-----\n%s\n-----END UNIDOC LICENSE KEY-----", offlineLicenseKey)

	err := license.SetLicenseKey(ofk, customerName)
	if err != nil {
		panic(err)
	}
}

func TestFunc(t *testing.T) {
	lk := license.GetLicenseKey()
	if lk == nil {
		fmt.Printf("Failed retrieving license key")
		return
	}
	fmt.Printf("License: %s\n", lk.ToString())
}

@ipod4g
Copy link

ipod4g commented Aug 28, 2024

@JoeEdwards-GloveBox We tested your script using two different versions, and it's working well, confirming that the license is valid. If you encounter any issues with your license, please reach out to us through the customer portal, and we'll resolve it for you.
https://unidoc.atlassian.net/servicedesk/customer/portal/8

@JoeEdwards-GloveBox
Copy link
Author

@ipod4g I've added the engineer who was experiencing this error on the support thread to help him narrow down the specific issue and why he's receiving the expired key message only when using this version of unidoc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants