[GH-ISSUE #33] Activation fails on RHEL 8.9 #26

New issue

Closed

opened 2026-02-27 23:03:28 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @Weingartens on GitHub (Feb 4, 2024).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/33

Installed Pritunl v1.32.3732.84 9b38bc today on Oracle Linux 8.9 (according to the official instructions), then exceuted setup.py with root rights apparently successful:

[root@localhost ~]# python3 setup.py 
  ____       _ _               _   _____     _             _    ____ ___ 
 |  _ \ _ __(_) |_ _   _ _ __ | | |  ___|_ _| | _____     / \  |  _ \_ _|
 | |_) | '__| | __| | | | '_ \| | | |_ / _` | |/ / _ \   / _ \ | |_) | | 
 |  __/| |  | | |_| |_| | | | | | |  _| (_| |   <  __/  / ___ \|  __/| | 
 |_|   |_|  |_|\__|\__,_|_| |_|_| |_|  \__,_|_|\_\___| /_/   \_\_|  |___|
                                                                         
[I]nstall, [R]eset, [B]uy Pritunl, [Q]uit? i

By default, the Pritunl API endpoint is hosted at "app.pritunl.com".
In case you want to use your own instance, you also have to support HTTPS!
Note, that the SSO implementation of Pritunl is hosted at their servers (closed source) and will just be "disabled".
Please enter the new API endpoint [pritunl-api.simonmicro.de]: 
Okay. We will change "app.pritunl.com" to "pritunl-api.simonmicro.de" and "auth.pritunl.com" to "pritunl-api.simonmicro.de/auth/" now...
[1/5] Replacing in /usr/lib/python3.6...
[2/5] Replacing in /usr/lib/pritunl/...
[3/5] Replacing in /usr/share/pritunl/www/...
[4/5] Replacing in /usr/lib/pritunl/...
[5/5] Replacing in /usr/share/pritunl/www/...
Modified 5 files in 5 paths.
Please make sure to restart the Pritunl daemon now and please support the developer.

All looks good for me:

But I can't enter a key:

Does the script no longer work or am I doing something wrong? Please note that also bad premium or active ultimate not working. Same error as above in the screenshots.
I restarted the daemon and the server several times. If I should post logs please say which ones.

Thanks.

Originally created by @Weingartens on GitHub (Feb 4, 2024). Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/33 Installed Pritunl v1.32.3732.84 9b38bc today on Oracle Linux 8.9 (according to the [official instructions](https://docs.pritunl.com/docs/pritunl-zero-service#install)), then exceuted _setup.py_ with root rights apparently successful: ``` [root@localhost ~]# python3 setup.py ____ _ _ _ _____ _ _ ____ ___ | _ \ _ __(_) |_ _ _ _ __ | | | ___|_ _| | _____ / \ | _ \_ _| | |_) | '__| | __| | | | '_ \| | | |_ / _` | |/ / _ \ / _ \ | |_) | | | __/| | | | |_| |_| | | | | | | _| (_| | < __/ / ___ \| __/| | |_| |_| |_|\__|\__,_|_| |_|_| |_| \__,_|_|\_\___| /_/ \_\_| |___| [I]nstall, [R]eset, [B]uy Pritunl, [Q]uit? i By default, the Pritunl API endpoint is hosted at "app.pritunl.com". In case you want to use your own instance, you also have to support HTTPS! Note, that the SSO implementation of Pritunl is hosted at their servers (closed source) and will just be "disabled". Please enter the new API endpoint [pritunl-api.simonmicro.de]: Okay. We will change "app.pritunl.com" to "pritunl-api.simonmicro.de" and "auth.pritunl.com" to "pritunl-api.simonmicro.de/auth/" now... [1/5] Replacing in /usr/lib/python3.6... [2/5] Replacing in /usr/lib/pritunl/... [3/5] Replacing in /usr/share/pritunl/www/... [4/5] Replacing in /usr/lib/pritunl/... [5/5] Replacing in /usr/share/pritunl/www/... Modified 5 files in 5 paths. Please make sure to restart the Pritunl daemon now and please support the developer. ``` All looks good for me: ![2024-02-04_21h39_17](https://github.com/simonmicro/Pritunl-Fake-API/assets/131807776/4c4a8f37-8193-4093-9f7d-34355b20ddd1) But I can't enter a key: ![2024-02-04_21h22_29](https://github.com/simonmicro/Pritunl-Fake-API/assets/131807776/b316b2ab-5221-42e1-b5cb-a1fc1b4f89fc) Does the script no longer work or am I doing something wrong? Please note that also bad premium or active ultimate not working. Same error as above in the screenshots. I restarted the daemon and the server several times. If I should post logs please say which ones. Thanks.