-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scproxy sudden stopped working #4
Comments
Hi, thanks for your bug report. That is strange, I'm using it successfully. Running the commands you give above, works for me. |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I have enjoyed your bypass-solution for over two months now. Today it suddenly stopped working. I have tried with differ user-switcher agent to no awail. Scproxy also stopped working on my colleagues computer. Could there be some new update ByPass that stops your script from working?
#TEST1
systemd-socket-activate -l 31505 python3 scproxy.py
Listening on [::]:31505 as 3.
Communication attempt on fd 3.
Execing python3 (python3 scproxy.py)
^CTraceback (most recent call last):
File "/home/user/scproxy/scproxy.py", line 236, in
httpd.handle_request()
File "/usr/lib64/python3.12/socketserver.py", line 297, in handle_request
if selector.select(timeout):
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.12/selectors.py", line 415, in select
fd_event_list = self._selector.poll(timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#TEST2
curl --insecure -H 'Sec-Fetch-Mode: cors' -H 'Origin: https://secure.buypass.no' \
--data-raw '' https://127.0.0.1:31505/scard/list/
curl: (7) Failed to connect to 127.0.0.1 port 31505 after 0 ms: Couldn't connect to server
The text was updated successfully, but these errors were encountered: