[GH-ISSUE #28] New version v1.32.3498.90 cba2e5 #23

Closed
opened 2026-02-27 23:03:27 +03:00 by kerem · 20 comments
Owner

Originally created by @rfdrew on GitHub (Apr 17, 2023).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/28

image v1.32.3498.90 cba2e5
Originally created by @rfdrew on GitHub (Apr 17, 2023). Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/28 <img width="753" alt="image" src="https://user-images.githubusercontent.com/20803599/232415832-54e30ea9-a274-4b86-9872-a84f02ff9ff5.png"> v1.32.3498.90 cba2e5
kerem closed this issue 2026-02-27 23:03:27 +03:00
Author
Owner

@royalhaze commented on GitHub (Apr 21, 2023):

same issue , i try it on many version and still not working

<!-- gh-comment-id:1517634734 --> @royalhaze commented on GitHub (Apr 21, 2023): same issue , i try it on many version and still not working
Author
Owner

@royalhaze commented on GitHub (Apr 21, 2023):

same issue , i try it on many version and still not working

this bug happened because browser unable to load subscription style file in some case
/subscription/styles/enterprise_plus/1003235044068.css
this page response with internal server error

<!-- gh-comment-id:1517659731 --> @royalhaze commented on GitHub (Apr 21, 2023): > same issue , i try it on many version and still not working this bug happened because browser unable to load subscription style file in some case /subscription/styles/enterprise_plus/1003235044068.css this page response with internal server error
Author
Owner

@simonmicro commented on GitHub (Apr 22, 2023):

Wait - internal server error on Python or on the fake-api backend?

<!-- gh-comment-id:1518645804 --> @simonmicro commented on GitHub (Apr 22, 2023): Wait - internal server error on Python or on the fake-api backend?
Author
Owner

@Moaaz-0x commented on GitHub (Apr 22, 2023):

I believe it's Python error, as you can see the request came from my server
error

<!-- gh-comment-id:1518674669 --> @Moaaz-0x commented on GitHub (Apr 22, 2023): I believe it's Python error, as you can see the request came from my server ![error](https://user-images.githubusercontent.com/21114760/233791010-fe41e2e8-3571-4d64-a616-5fc21971de8b.png)
Author
Owner

@Moaaz-0x commented on GitHub (Apr 22, 2023):

Although I have updated Pritunl to v1.32.3504.68 and still has the same error

<!-- gh-comment-id:1518675162 --> @Moaaz-0x commented on GitHub (Apr 22, 2023): Although I have updated Pritunl to `v1.32.3504.68` and still has the same error
Author
Owner

@royalhaze commented on GitHub (Apr 28, 2023):

Although I have updated Pritunl to v1.32.3504.68 and still has the same error

just use this installation script
royalhaze/pritunl-install

it use v1.30.3108.50

<!-- gh-comment-id:1527500881 --> @royalhaze commented on GitHub (Apr 28, 2023): > Although I have updated Pritunl to `v1.32.3504.68` and still has the same error just use this installation script [royalhaze/pritunl-install](https://github.com/royalhaze/pritunl-install) it use v1.30.3108.50
Author
Owner

@Vlad1mir-D commented on GitHub (Apr 29, 2023):

This issue was caused by these two commits and some invisible updates on the real API side:

So the latest version which works properly with the current version of Fake API is https://github.com/pritunl/pritunl/releases/tag/1.32.3457.59
There is a chance I'll update API if someone won't make it before but it's definitely going take a loong while as I'm currently very limited in my spare time.

<!-- gh-comment-id:1528648854 --> @Vlad1mir-D commented on GitHub (Apr 29, 2023): This issue was caused by these two commits and some invisible updates on the real API side: - https://github.com/pritunl/pritunl/commit/d523e4869894240ef105e3c3f3787513b4dc5559 - https://github.com/pritunl/pritunl/commit/c7bb723965407cf8061b9bbaf3c903c3dc369941 So the latest version which works properly with the current version of Fake API is https://github.com/pritunl/pritunl/releases/tag/1.32.3457.59 There is a chance I'll update API if someone won't make it before but it's definitely going take a loong while as I'm currently very limited in my spare time.
Author
Owner

@Vlad1mir-D commented on GitHub (Apr 29, 2023):

Ah, it seems there are additional commits which prevents proper interaction with an API via Web:

So if interactive Fake API options (such as license change) are required it's even worse: in this case we're capped at https://github.com/pritunl/pritunl/releases/tag/1.30.3431.73

NVM, https://github.com/pritunl/pritunl/releases/tag/1.32.3457.59 works fine

<!-- gh-comment-id:1528671930 --> @Vlad1mir-D commented on GitHub (Apr 29, 2023): ~~Ah, it seems there are additional commits which prevents proper interaction with an API via Web:~~ - ~~https://github.com/pritunl/pritunl/commit/0b600799d2dcee23b54538e0fdb300d25d67921d~~ - ~~https://github.com/pritunl/pritunl/commit/4677814f88ac5aa5c708b6bcbc6dc9ef96c73d0a~~ ~~So if interactive Fake API options (such as license change) are required it's even worse: in this case we're capped at https://github.com/pritunl/pritunl/releases/tag/1.30.3431.73~~ NVM, https://github.com/pritunl/pritunl/releases/tag/1.32.3457.59 works fine
Author
Owner

@simonmicro commented on GitHub (May 1, 2023):

Oh boi. @Vlad1mir-D any PRs are more than welcome - as I also have very limited time at the moment. But I'm pretty sure, that we can figure something out...

<!-- gh-comment-id:1529831513 --> @simonmicro commented on GitHub (May 1, 2023): Oh boi. @Vlad1mir-D any PRs are more than welcome - as I also have very limited time at the moment. But I'm pretty sure, that we can figure something out...
Author
Owner

@Vlad1mir-D commented on GitHub (May 2, 2023):

I've managed to implement a dirty workaround so it's time to fix a few things and I'll be able to publish a solution for 1.32.3457.59 but I can't give any ETA.

<!-- gh-comment-id:1530885436 --> @Vlad1mir-D commented on GitHub (May 2, 2023): I've managed to implement a [dirty workaround](https://github.com/Vlad1mir-D/Pritunl-Fake-API/pull/new/dirty-fix-for-1003234794095) so it's time to fix a few things and I'll be able to publish a solution for 1.32.3457.59 but I can't give any ETA.
Author
Owner

@niyazialpay commented on GitHub (May 6, 2023):

I'm having trouble same thing

<!-- gh-comment-id:1537091036 --> @niyazialpay commented on GitHub (May 6, 2023): I'm having trouble same thing
Author
Owner

@tobiasredel commented on GitHub (May 16, 2023):

I am also looking for a fix. Great effort. Thanks @simonmicro

<!-- gh-comment-id:1549042973 --> @tobiasredel commented on GitHub (May 16, 2023): I am also looking for a fix. Great effort. Thanks @simonmicro
Author
Owner

@niyazialpay commented on GitHub (May 17, 2023):

I found that the issue is caused by the CSS file at the "/subscription/styles/enterprise_plus/1003235334094.css" address returning a 500 error. I noticed that this address is defined in the file "/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/handlers/subscription.py" with the line "@app.app.route('/subscription/styles//.css', methods=['GET'])". To resolve the problem, I commented out the entire "if styles['etag'] and styles['data']" command block in this route definition and restarted the service, which fixed the issue. You can create a function that can be used to remove or comment out this section after the replace step in the Fake API script for intervention.

<!-- gh-comment-id:1552150920 --> @niyazialpay commented on GitHub (May 17, 2023): I found that the issue is caused by the CSS file at the "/subscription/styles/enterprise_plus/1003235334094.css" address returning a 500 error. I noticed that this address is defined in the file "/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/handlers/subscription.py" with the line "@app.app.route('/subscription/styles/<plan>/<ver>.css', methods=['GET'])". To resolve the problem, I commented out the entire "if styles['etag'] and styles['data']" command block in this route definition and restarted the service, which fixed the issue. You can create a function that can be used to remove or comment out this section after the replace step in the Fake API script for intervention.
Author
Owner

@Vlad1mir-D commented on GitHub (May 19, 2023):

@niyazialpay just read the https://github.com/simonmicro/Pritunl-Fake-API/issues/28#issuecomment-1528648854

<!-- gh-comment-id:1554400484 --> @Vlad1mir-D commented on GitHub (May 19, 2023): @niyazialpay just read the https://github.com/simonmicro/Pritunl-Fake-API/issues/28#issuecomment-1528648854
Author
Owner

@simonmicro commented on GitHub (May 21, 2023):

Done - fixed and live.

<!-- gh-comment-id:1556196726 --> @simonmicro commented on GitHub (May 21, 2023): Done - fixed and live.
Author
Owner

@Vlad1mir-D commented on GitHub (May 29, 2023):

Thanks @simonmicro!
I'm glad my code helped a little :)

<!-- gh-comment-id:1567582880 --> @Vlad1mir-D commented on GitHub (May 29, 2023): Thanks @simonmicro! I'm glad my code helped a little :)
Author
Owner

@rfdrew commented on GitHub (Jun 3, 2023):

many thanks!!!!

<!-- gh-comment-id:1575013678 --> @rfdrew commented on GitHub (Jun 3, 2023): many thanks!!!!
Author
Owner

@amirhmoradi commented on GitHub (Jul 23, 2023):

I am still facing this issue on latest pritunl v1.32.3552.76 3f54d8

<!-- gh-comment-id:1646897897 --> @amirhmoradi commented on GitHub (Jul 23, 2023): I am still facing this issue on latest pritunl v1.32.3552.76 3f54d8
Author
Owner

@simonmicro commented on GitHub (Jul 30, 2023):

@amirhmoradi Could you further describe your setup please? It seems strange that you report this error, while most users are happy. Could it be that your PHP version is outdated?

<!-- gh-comment-id:1657233871 --> @simonmicro commented on GitHub (Jul 30, 2023): @amirhmoradi Could you further describe your setup please? It seems strange that you report this error, while most users are happy. Could it be that your PHP version is outdated?
Author
Owner

@amirhmoradi commented on GitHub (Jul 30, 2023):

@simonmicro it was my error, sorry.
I had an old version running on the server and mixed up my setup.
Everything seems to be working fine indeed. Thanks for the great work.

<!-- gh-comment-id:1657252486 --> @amirhmoradi commented on GitHub (Jul 30, 2023): @simonmicro it was my error, sorry. I had an old version running on the server and mixed up my setup. Everything seems to be working fine indeed. Thanks for the great work.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Pritunl-Fake-API#23
No description provided.