Px Proxy Issue on Windows 10

[mailman-2097]

Having issues in px-proxy which was installed from the full windows release

Both Windows and Generic credentials added in Control Panel

Px

debug logs

debug-Process-1.log
debug-MainProcess.log

px started as follows

px --foreground --debug

environment vars set

HTTP_PROXY                     http://localhost:3128
HTTPS_PROXY                    http://localhost:3128

Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:server = xxxx.xxxxx.xxxxxxxx.xxx:40101
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:pac =
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:listen = 127.0.0.1
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:port = 3128
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:gateway = 0
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:hostonly = 0
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:allow = *.*.*.*
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:noproxy =
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:useragent =
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:username = Px
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: proxy:auth =
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:workers = 2
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:threads = 5
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:idle = 30
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:socktimeout = 20.0
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:proxyreload = 60
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:foreground = 1
Process-1: MainThread: 1657603176: /run/start_worker/print_banner: settings:log = 0
MainProcess: MainThread: 1657603264: /serve_forever/_handle_request_noblock/verify_request: Client address: 127.0.0.1
MainProcess: Thread_0: 1657603264: /do_CONNECT/do_curl/__init__: 1dcb838e2129b471a33b074eafc9980f15ccef4b: New curl instance
MainProcess: Thread_0: 1657603264: /do_curl/__init__/_setup: 1dcb838e2129b471a33b074eafc9980f15ccef4b: CONNECT releases.hashicorp.com:443 using HTTP/1.1
MainProcess: Thread_0: 1657603264: /handle_one_request/do_CONNECT/do_curl: 1dcb838e2129b471a33b074eafc9980f15ccef4b: Path = releases.hashicorp.com:443
MainProcess: Thread_0: 1657603264: /find_proxy_for_url/find_proxy_for_url/get_netloc: netloc = ('releases.hashicorp.com', 443), path = /
MainProcess: Thread_0: 1657603264: /do_CONNECT/do_curl/get_destination: 1dcb838e2129b471a33b074eafc9980f15ccef4b: Proxy = [('ehlh.swproxy.nswhealth.net', 40101)]
MainProcess: Thread_0: 1657603264: /handle_one_request/do_CONNECT/do_curl: 1dcb838e2129b471a33b074eafc9980f15ccef4b: Configuring proxy settings
----------------------------------------
Exception occurred during processing of request from ('127.0.0.1', 53678)
Traceback (most recent call last):
  File "C:\Tools\px\socketserver.py", line 683, in process_request_thread
  File "C:\Tools\px\socketserver.py", line 360, in finish_request
  File "C:\Tools\px\socketserver.py", line 747, in __init__
  File "C:\Tools\px\http\server.py", line 425, in handle
  File "C:\Tools\px\px\main.py", line 295, in handle_one_request
  File "C:\Tools\px\http\server.py", line 413, in handle_one_request
  File "C:\Tools\px\px\main.py", line 392, in do_CONNECT
  File "C:\Tools\px\px\main.py", line 340, in do_curl
  File "C:\Tools\px\keyring\core.py", line 55, in get_password
  File "C:\Tools\px\keyring\backends\fail.py", line 25, in get_password
keyring.errors.NoKeyringError: No recommended backend was available. Install a recommended 3rd party backend package; or, install the keyrings.alt package if you want to use the non-recommended backends. See https://pypi.org/project/keyring for details.
----------------------------------------

Please can somone assist..

[mailman-2097]

https://www.automatedops.com/blog/2013/06/07/get-storedcredentials-module/
I was able to follow above blog post to see if the storedcreds were accessible, and that worked..
it would be great to get the px tool running to avoid all the powershell overhead

[mailman-2097]

debug-MainProcess.log
debug-Process-1.log

I tried installing from python pip in virtual environment, but still no luck..

[mailman-2097]

I used the python px command to save the creds in windows cred manager..
and noticed the correct format in saving the credential..
I reverted back to my windows standalone px and pointed to the previously save generic credential and restarted the proxy tool did not work..
if I try to save the credential again from the windows standalone px.. it was not able to save ..
I am running this is privileged mode..

PS C:\Users\xxx> px --username=xxx\xxx --password
Setting password for 'xxx\xxx'
Enter password:

Traceback (most recent call last):
  File "C:\Tools\px\px.py", line 3, in <module>
  File "C:\Tools\px\px\main.py", line 1087, in main
  File "C:\Tools\px\px\main.py", line 836, in parse_config
  File "C:\Tools\px\px\main.py", line 598, in set_password
  File "C:\Tools\px\keyring\core.py", line 60, in set_password
  File "C:\Tools\px\keyring\backends\fail.py", line 25, in get_password
keyring.errors.NoKeyringError: No recommended backend was available. Install a recommended 3rd party backend package; or, install the keyrings.alt package if you want to use the non-recommended backends. See https://pypi.org/project/keyring for details.

[genotrance]

This is a valid issue and will be fixed shortly. I'll track it in #158.

[genotrance]

This is now fixed.