mirror of
https://github.com/simonmicro/Pritunl-Fake-API.git
synced 2026-04-26 07:36:00 +03:00
[GH-ISSUE #29] "Server error occurred" on current version during activation #22
Labels
No labels
bug
bug
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Pritunl-Fake-API#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @UltimateABC on GitHub (May 22, 2023).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/29
hi
can i ask which version is working fine?
i tested many of them and all of tested on ubuntu , i got an error
Server error occurred, please try again later. message
maybe my installation method is wrong, is there any step by step tutorials here?
@rfdrew commented on GitHub (May 23, 2023):
+1 I have some error.



@simonmicro commented on GitHub (May 23, 2023):
34ff12f64f@simonmicro commented on GitHub (May 23, 2023):
Additionally, I can observe a large amount of
473errors on my api endpoint, as many users are trying to activate using too old clients (but no 500 -> so no server failures). I think they have to restart their Pritunl instance to view the notification, pointing out their too old client. Well... 🤷♂️If you are affected, try checkout your instance logs and see if you have something interesting there 😉
Edit:
a76ad96f96@UltimateABC commented on GitHub (May 24, 2023):
i changed the endpoint API to your and worked fine.
thanks
@UltimateABC commented on GitHub (May 24, 2023):
i tested on ubuntu 22.04
i dont know if below steps are required or not, im not sure about cloning pritunel git data
do the suggested commands by site
used below code to activate enterprise version
@nd4y commented on GitHub (May 25, 2023):
I deployed a FakeAPI server using a Self-Signed certificate.
After adding the root certificate to the trusted list in
/etc/ssl/certs/ca-certificates.crton Pritunl, I still gotrequests.exceptions.SSLError: HTTPSConnectionPool(host='pritunl-fakeapi.local', port=443) error: Max retries exceeded with url: /subscription (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)'))).I found out that they use their own Python as part of the pritunl distribution and you need to add the root certificate to
/usr/lib/pritunl/usr/lib/python3.9/site-packages/certifi/cacert.pem@YuSyA55 commented on GitHub (Mar 20, 2025):
Good day.
Please tell me how you solved this error.
How can I correctly import my CA into this file?
@nd4y commented on GitHub (Mar 20, 2025):
@YuSyA55 , Good day!
cat ca.crt.pem | tee -a /usr/lib/pritunl/usr/lib/python3.9/site-packages/certifi/cacert.pemca.crt.pem contains the certificate in PEM format
@YuSyA55 commented on GitHub (Mar 20, 2025):
It works! Thanks!!!