mirror of
https://github.com/simonmicro/Pritunl-Fake-API.git
synced 2026-04-26 07:36:00 +03:00
[GH-ISSUE #18] Update for Pritunl v1.30.3108.50 #17
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#17
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 @MANKUD on GitHub (Mar 17, 2022).
Original GitHub issue: https://github.com/simonmicro/Pritunl-Fake-API/issues/18
Originally assigned to: @simonmicro on GitHub.
Hello,
Could you please try to make your API work for the latest release pritunl v1.30.3108.50 as this release contains a fix for port forwarding on wireguard which is very crucial. if you are able to do it I would love to make a donation to support you.
@simonmicro commented on GitHub (Mar 17, 2022):
Sure thing! Could you provide any logs what the current problem is? There is a good chance, that you have just missed to reapply the patch after updating 😁
@MANKUD commented on GitHub (Mar 17, 2022):
Hello,
I have tried it on a fresh installation on the latest release its just that
it says the license is activated as I remember but nothing happens.
@MANKUD commented on GitHub (Mar 18, 2022):
The logs when I had checked it said invalid key.
@MANKUD commented on GitHub (Mar 18, 2022):
Hello,
Would you be able to help me I would really appreciate it and maybe we can have a look together if you have time.
@MANKUD commented on GitHub (Mar 18, 2022):
Here are a few screenshots.
@simonmicro commented on GitHub (Mar 18, 2022):
🤣 - I see:
github.com/pritunl/pritunl@c1772d9b32Guess I have to update the script to work with that... This will take a while, as I have pretty much no time 😁
@MANKUD commented on GitHub (Mar 18, 2022):
Oh, I see that now he has encoded it using base64. Will it be so hard since base64 is used?
@simonmicro commented on GitHub (Mar 18, 2022):
No, but I will NOT update the setup for that - at least not using bash. I guess a few lines of Python will be enough for the future.
@MANKUD commented on GitHub (Mar 18, 2022):
oh ok, may I know a timeline maybe? when can we expect an update from your end?
@simonmicro commented on GitHub (Mar 18, 2022):
Could you be my BETA tester? Try this: setup.py.zip
@MANKUD commented on GitHub (Mar 18, 2022):
sure I would love to let me try this :)
@simonmicro commented on GitHub (Mar 18, 2022):
Nvm, I had not tested the script - it is broken... Working on that...
@simonmicro commented on GitHub (Mar 18, 2022):
2nd try setup.py.zip
@MANKUD commented on GitHub (Mar 18, 2022):
yes, I tried and it seems like its broken as you mentioned.
BTW I downgraded to pritunl v1.30.3102.46 (last version supported by your current fake API)and then ran your script which worked fine after that I manually replaced the wg port forwarding fix files i.e clients.py and instance.py and now the wg fix is working on an older version where your old fake api works.
@MANKUD commented on GitHub (Mar 18, 2022):
let me give it a try
@MANKUD commented on GitHub (Mar 18, 2022):
does not seem to be working I have to run this instead of your old script right?
@simonmicro commented on GitHub (Mar 18, 2022):
Yes, this is strange... I'm investigating...
@MANKUD commented on GitHub (Mar 18, 2022):
oh ok no problem take your time :)
@MANKUD commented on GitHub (Mar 18, 2022):
Hi, the script ran successfully but the fake API emulation is not working.
@MANKUD commented on GitHub (Mar 18, 2022):
no pop up here
@MANKUD commented on GitHub (Mar 18, 2022):
@simonmicro commented on GitHub (Mar 18, 2022):
Here we go again: setup.py.zip
@MANKUD commented on GitHub (Mar 18, 2022):
oh ok great that was quick let me try.
@MANKUD commented on GitHub (Mar 18, 2022):
looks like added 3 more things.
@MANKUD commented on GitHub (Mar 18, 2022):
looks like it did not work I cannot see advanced options for users :(
@MANKUD commented on GitHub (Mar 18, 2022):
@simonmicro commented on GitHub (Mar 18, 2022):
Yes, I've just seen that error. Looks like they changed how the CSS file is passed on...
@MANKUD commented on GitHub (Mar 18, 2022):
so it means more digging into it and adding more lines of code into the script?
@simonmicro commented on GitHub (Mar 18, 2022):
Theoretically I just have to mitigate
github.com/pritunl/pritunl@70b354a10don my side......on it...
@simonmicro commented on GitHub (Mar 18, 2022):
Done. I'll push everything soon ™️
Can you confirm?
@MANKUD commented on GitHub (Mar 18, 2022):
confirm? I did not understand tell me what I need to do?
@simonmicro commented on GitHub (Mar 18, 2022):
Just restart your server after applying the script. I've just updated the api endpoint to be compatible with the newest version!
@MANKUD commented on GitHub (Mar 18, 2022):
ok I am on it.
@MANKUD commented on GitHub (Mar 18, 2022):
OMG perfect you are awesome looks like it is finally fixed.
@MANKUD commented on GitHub (Mar 18, 2022):
check your sponsor's page :)
@simonmicro commented on GitHub (Mar 18, 2022):
Thank you very much 😊 🤯
@MANKUD commented on GitHub (Mar 21, 2022):
Hello,
The script seems to be broken again on the latest release. Maybe the developer has again changed something.
@simonmicro commented on GitHub (Mar 21, 2022):
Just making sure: You rerun the
setup.pyafter updating? Because I do not see any relevant code changes...@MANKUD commented on GitHub (Mar 21, 2022):
Yes, I already tried that it does not fix it. I think the changes are hidden this time may be as I too did not find any significant changes in the code related to this.
@MANKUD commented on GitHub (Mar 21, 2022):
@simonmicro commented on GitHub (Mar 21, 2022):
Sadly both the Docker image (
goofball222/pritunl) and the Debian packages (https://repo.pritunl.com/stable/apt/pool/) do not contain this version yet. Therefore I'm unable to investigate this (yet). Feel free to open up a new issue if the problem persist (even after a cold-boot of the server - maybe some caching is going on here?). Overall this seems very strange...@MANKUD commented on GitHub (Mar 21, 2022):
What I noticed is that the latest release is usually not available as a package update via the repository and we have to manually download it using wget package name and then run dpkg -i package name to manually update to the latest release.
@simonmicro commented on GitHub (Mar 21, 2022):
Argh sh*t. here we go again:
github.com/pritunl/pritunl@97f08a9ad6Please open a new issue for this - that will take a while... I guess this only affects the subscription UI...
@MANKUD commented on GitHub (Mar 21, 2022):
Yes, right I was about to share the same. Looks like the developer is following Pritunl-Fake-AP very closely 🤣
Alright, I will open a new issue and you can take your time for this one no problem 😄
@MANKUD commented on GitHub (Mar 21, 2022):
I see this now will it be even possible anymore?
cipher = Cipher(
algorithms.AES(key),
@simonmicro commented on GitHub (Mar 21, 2022):
Yes, it is - he uses symmetric encryption with not-so-secret secrets... BUT the faked API is written in PHP, so getting the proper "encryption" (more an obfuscation) running on the api side will be very challenging. Maybe I'll just ship a patch with the
setup.pywhich reverts that "feature", but this is a little more intrusive than just changing the hard-coded endpoint URL. I'll have to think about this and won't fix this just as fast as his previous breaking change.@MANKUD commented on GitHub (Mar 21, 2022):
I totally understand and I would love to test it whenever you are able to make a patch for pritunl v1.30.3112.0 😄