[GH-ISSUE #29] "Server error occurred" on current version during activation #22

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

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

image

maybe my installation method is wrong, is there any step by step tutorials here?

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 ![image](https://github.com/simonmicro/Pritunl-Fake-API/assets/3676067/23309aba-3634-4a0e-bf2b-725e4c29c1fb) maybe my installation method is wrong, is there any step by step tutorials here?
kerem closed this issue 2026-02-27 23:03:27 +03:00
Author
Owner

@rfdrew commented on GitHub (May 23, 2023):

+1 I have some error.
image
image
image

<!-- gh-comment-id:1558525673 --> @rfdrew commented on GitHub (May 23, 2023): +1 I have some error. ![image](https://github.com/simonmicro/Pritunl-Fake-API/assets/20803599/4b3d2fbf-c791-4ec0-93b3-f76c5cc4b53b) ![image](https://github.com/simonmicro/Pritunl-Fake-API/assets/20803599/c04dab1c-1ba6-41f7-a0b1-5d69e7298dc2) ![image](https://github.com/simonmicro/Pritunl-Fake-API/assets/20803599/2d72bcdd-733b-4fc6-8fa9-cf8110bc0ef5)
Author
Owner

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

  1. Are you using an own hosted endpoint? If yes, does this error also appear on the public one?
  2. Make sure to use PHP 8+. PHP 7 is end-of-life and the API now uses some functions from PHP 8 to make my life easier.
  3. For you guys: 34ff12f64f
<!-- gh-comment-id:1560107904 --> @simonmicro commented on GitHub (May 23, 2023): 1. Are you using an own hosted endpoint? If yes, does this error also appear on the public one? 2. Make sure to use PHP 8+. PHP 7 is end-of-life and the API now uses some functions from PHP 8 to make my life easier. 3. For you guys: 34ff12f64faa4cb167f67434aa63b7e72e9b20b0
Author
Owner

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

Additionally, I can observe a large amount of 473 errors 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

<!-- gh-comment-id:1560123664 --> @simonmicro commented on GitHub (May 23, 2023): Additionally, I can observe a **large** amount of `473` errors 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... :man_shrugging: If you are affected, try checkout your instance logs and see if you have something interesting there :wink: Edit: a76ad96f96c945499a5a1ace413d7d60e98edba5
Author
Owner

@UltimateABC commented on GitHub (May 24, 2023):

i changed the endpoint API to your and worked fine.
thanks

<!-- gh-comment-id:1560763573 --> @UltimateABC commented on GitHub (May 24, 2023): i changed the endpoint API to your and worked fine. thanks
Author
Owner

@UltimateABC commented on GitHub (May 24, 2023):

i tested on ubuntu 22.04

sudo tee /etc/apt/sources.list.d/pritunl.list << EOF
deb http://repo.pritunl.com/stable/apt jammy main
EOF

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv 7568D9BB55FF9E5287D586017AE645C0CF8E292A

curl https://raw.githubusercontent.com/pritunl/pgp/master/pritunl_repo_pub.asc | sudo apt-key add -

sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list << EOF
deb https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 multiverse
EOF

wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add -


apt --fix-broken install

sudo apt update

sudo apt --assume-yes upgrade

sudo apt -y install wireguard wireguard-tools

sudo ufw disable

sudo apt -y install pritunl mongodb-org

sudo systemctl enable mongod pritunl

sudo systemctl start mongod pritunl

reboot


sudo sh -c 'echo "* hard nofile 64000" >> /etc/security/limits.conf'
sudo sh -c 'echo "* soft nofile 64000" >> /etc/security/limits.conf'
sudo sh -c 'echo "root hard nofile 64000" >> /etc/security/limits.conf'
sudo sh -c 'echo "root soft nofile 64000" >> /etc/security/limits.conf'
  • open site based on my public ip

i dont know if below steps are required or not, im not sure about cloning pritunel git data

mkdir -p /pritunfakeapi && cd /pritunfakeapi

wget https://github.com/simonmicro/Pritunl-Fake-API/archive/refs/heads/master.zip && unzip master.zip && sleep 1 && rm -f master.zip 

cd /pritunfakeapi/Pritunl-Fake-API-master/server

wget https://github.com/pritunl/pritunl/archive/refs/heads/master.zip && unzip master.zip && sleep 1 && rm -f master.zip 

python3 setup.py

# go with default values

  • open site by enetering public IP on browser

do the suggested commands by site

sudo pritunl setup-key

sudo pritunl default-password

used below code to activate enterprise version

active ultimate
<!-- gh-comment-id:1560777169 --> @UltimateABC commented on GitHub (May 24, 2023): i tested on ubuntu 22.04 ``` sudo tee /etc/apt/sources.list.d/pritunl.list << EOF deb http://repo.pritunl.com/stable/apt jammy main EOF sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv 7568D9BB55FF9E5287D586017AE645C0CF8E292A curl https://raw.githubusercontent.com/pritunl/pgp/master/pritunl_repo_pub.asc | sudo apt-key add - sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list << EOF deb https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 multiverse EOF wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add - apt --fix-broken install sudo apt update sudo apt --assume-yes upgrade sudo apt -y install wireguard wireguard-tools sudo ufw disable sudo apt -y install pritunl mongodb-org sudo systemctl enable mongod pritunl sudo systemctl start mongod pritunl reboot ``` ``` sudo sh -c 'echo "* hard nofile 64000" >> /etc/security/limits.conf' sudo sh -c 'echo "* soft nofile 64000" >> /etc/security/limits.conf' sudo sh -c 'echo "root hard nofile 64000" >> /etc/security/limits.conf' sudo sh -c 'echo "root soft nofile 64000" >> /etc/security/limits.conf' ``` * open site based on my public ip i dont know if below steps are required or not, im not sure about cloning pritunel git data ``` mkdir -p /pritunfakeapi && cd /pritunfakeapi wget https://github.com/simonmicro/Pritunl-Fake-API/archive/refs/heads/master.zip && unzip master.zip && sleep 1 && rm -f master.zip cd /pritunfakeapi/Pritunl-Fake-API-master/server wget https://github.com/pritunl/pritunl/archive/refs/heads/master.zip && unzip master.zip && sleep 1 && rm -f master.zip python3 setup.py # go with default values ``` * open site by enetering public IP on browser do the suggested commands by site ``` sudo pritunl setup-key sudo pritunl default-password ``` used below code to activate enterprise version ``` active ultimate ```
Author
Owner

@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.crt on Pritunl, I still got
requests.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

<!-- gh-comment-id:1563445218 --> @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.crt` on Pritunl, I still got ` requests.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`
Author
Owner

@YuSyA55 commented on GitHub (Mar 20, 2025):

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.crt on Pritunl, I still got requests.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

Good day.
Please tell me how you solved this error.
How can I correctly import my CA into this file?

<!-- gh-comment-id:2740557751 --> @YuSyA55 commented on GitHub (Mar 20, 2025): > 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.crt` on Pritunl, I still got ` requests.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` Good day. Please tell me how you solved this error. How can I correctly import my CA into this file?
Author
Owner

@nd4y commented on GitHub (Mar 20, 2025):

@YuSyA55 , Good day!

How can I correctly import my CA into this file?

cat ca.crt.pem | tee -a /usr/lib/pritunl/usr/lib/python3.9/site-packages/certifi/cacert.pem
ca.crt.pem contains the certificate in PEM format
Image

<!-- gh-comment-id:2740587907 --> @nd4y commented on GitHub (Mar 20, 2025): @YuSyA55 , Good day! > How can I correctly import my CA into this file? `cat ca.crt.pem | tee -a /usr/lib/pritunl/usr/lib/python3.9/site-packages/certifi/cacert.pem` ca.crt.pem contains the certificate in PEM format ![Image](https://github.com/user-attachments/assets/1f2c7719-df99-4688-a865-c39cad5b3906)
Author
Owner

@YuSyA55 commented on GitHub (Mar 20, 2025):

It works! Thanks!!!

<!-- gh-comment-id:2741416150 --> @YuSyA55 commented on GitHub (Mar 20, 2025): It works! Thanks!!!
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#22
No description provided.