[GH-ISSUE #13] Fake Api is not registering on the new version of Pritunl #11

New issue

Closed

opened 2026-02-27 23:03:22 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 23:03:22 +03:00

Owner

Originally created by @ZEROPOINTBRUH on GitHub (Oct 10, 2021).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/13

Originally assigned to: @simonmicro on GitHub.

[Apollo][2021-10-10 11:34:42,107][ERROR] Failed to check subscription status Traceback (most recent call last): File "/usr/lib/pritunl/lib/python3.7/site-packages/pritunl/subscription.py", line 51, in update raise ValueError('License key is invalid') ValueError: License key is invalid

Originally created by @ZEROPOINTBRUH on GitHub (Oct 10, 2021). Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/13 Originally assigned to: @simonmicro on GitHub. ` [Apollo][2021-10-10 11:34:42,107][ERROR] Failed to check subscription status Traceback (most recent call last): File "/usr/lib/pritunl/lib/python3.7/site-packages/pritunl/subscription.py", line 51, in update raise ValueError('License key is invalid') ValueError: License key is invalid `

kerem

2026-02-27 23:03:22 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 23:03:23 +03:00

Author

Owner

@simonmicro commented on GitHub (Oct 11, 2021):

What version exactly? A quick look into the source does not reveal any changes to the subscription handling since February. Could you describe how exactly you managed to archive this - please note the exact steps to reproduce this. I assume you updated Pritunl and forgot to re-apply this - am I right?

@simonmicro commented on GitHub (Oct 11, 2021): What version exactly? A quick look into the source does not reveal any changes to the subscription handling since February. Could you describe how exactly you managed to archive this - please note the exact steps to reproduce this. I assume you updated Pritunl and forgot to re-apply this - am I right?

kerem commented

2026-02-27 23:03:23 +03:00

Author

Owner

@EclipseKnight commented on GitHub (Oct 12, 2021):

Hi I just encountered the same issue on a fresh install of pritunl on a fresh ubuntu live server 20.04 vm.

I have 2 hosts in a cluster connecting to a mongodb server.
The working host is running v1.29.2664.67
The not working host is running v1.30.2945.60

Edit: I just ran a git clone from this repo as well so it's using the latest commit.

@EclipseKnight commented on GitHub (Oct 12, 2021): Hi I just encountered the same issue on a fresh install of pritunl on a fresh ubuntu live server 20.04 vm. I have 2 hosts in a cluster connecting to a mongodb server. The working host is running v1.29.2664.67 The not working host is running v1.30.2945.60 Edit: I just ran a git clone from this repo as well so it's using the latest commit.

kerem commented

2026-02-27 23:03:23 +03:00

Author

Owner

@simonmicro commented on GitHub (Oct 13, 2021):

Hey, try the current version - I've tested it with Debian 10. It should work now (I'll update the api service in the next minutes).

@simonmicro commented on GitHub (Oct 13, 2021): Hey, try the current version - I've tested it with Debian 10. It should work now (I'll update the api service in the next minutes).