Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    genotrance
    @genotrance
    Might be a bit confusing but should not affect
    Seb
    @as1s
    just not sure if I set it up in a script will it respond with success?
    genotrance
    @genotrance
    Should work yes
    judikaelg
    @judikaelg
    Hello genotrance, I have been using px for a moment and it saved me multiple times with working behind the corporate proxy, so thanks a lot for this
    I am trying to use it now with a VM and i can't get to make it work
    The issue seemingly stems from not being able to access the proxy on another IP than localhost
    Here is my config :
    [proxy]
    server =
    port = 3128
    listen = 192.168.56.1
    allow = ...
    gateway = 0
    hostonly = 1
    noproxy = 127.0.0.1,192.168.56.0/24
    I also tried to listen on 0.0.0.0
    And i tried all combination of values for gateway/hostonly
    judikaelg
    @judikaelg
    When trying to use the proxy locally with any of my local IP the requests get dropped, but when using 127.0.0.1 it works
    Therefore I can't use it from my VM
    If you have any indication for further investigations I would really appreciate it
    Loriden
    @Loriden
    You aren't listening on your local IP, just 127.0.0.1 so your proxy isn't responding. Add your local IP as a listen and it'll work
    P.s you're likely listening on your default gateway...which px probably(?) Isn't installed on.
    judikaelg
    @judikaelg
    I don't understand, 192.168.56.1 is my local IP. It's a lan for VM addresses, and 192.168.56.1 is the host adress
    but i have tried listenning on all my adresses including 0.0.0.0
    (which should listen to all local adresses at once)
    judikaelg
    @judikaelg
    FYI, i moved forward on my issue
    I had the following conclusions : testing px proxy locally using the following commands :
    curl --proxy one_of_my_local_ip_adress www.github.com
    only works if using 127.0.0.1
    However from the VM I could access 10.0.2.2:3128
    which is another of the local host ip address, created by default by vagrant
    judikaelg
    @judikaelg
    So probably my issue was coming from the usage of "Host-Only adapter" on virtualbox, rather than "NAT" for network on my VM with Virtualbox
    ksimonova
    @ksimonova
    Hi, we got the tool installed and it works great. Thank you so much with your help in setting it up. I was wondering if you could give some background info on the security of using px behind corporate proxy and the handling of any sensitive data via Anaconda or other systems while using px?
    genotrance
    @genotrance
    hello ksimonova - security depends on SSPI so should be safe there
    we are leveraging python packages to help with auth, px only really contains http server code
    Jeronim Morina
    @plattenschieber

    Hey there, I can't get to work px and still have to rely on CNTML even though configuration seems the same (server, username). I tried installing a package via conda first with CNTLM - no errors. As soon as I switch to PX this resolved in the following error in conda:

    Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', RemoteDisconnected('Remote end closed connection without response'))': /pkgs/r/win-64/repodata.json

    and the following logs in PX:

    $ ./px.exe
    Serving at 127.0.0.1:3127 proc MainProcess
    MainProcess: MainThread: 1600865583: print_banner: proxy:server = proxy:8081
    MainProcess: MainThread: 1600865583: print_banner: proxy:port = 3127
    MainProcess: MainThread: 1600865583: print_banner: proxy:listen = 127.0.0.1
    MainProcess: MainThread: 1600865583: print_banner: proxy:allow = *.*.*.*
    MainProcess: MainThread: 1600865583: print_banner: proxy:gateway = 0
    MainProcess: MainThread: 1600865583: print_banner: proxy:hostonly = 0
    MainProcess: MainThread: 1600865583: print_banner: proxy:noproxy =
    MainProcess: MainThread: 1600865583: print_banner: proxy:useragent =
    MainProcess: MainThread: 1600865583: print_banner: settings:workers = 1
    MainProcess: MainThread: 1600865583: print_banner: settings:threads = 1
    MainProcess: MainThread: 1600865583: print_banner: settings:idle = 30
    MainProcess: MainThread: 1600865583: print_banner: settings:socktimeout = 20.0
    MainProcess: MainThread: 1600865583: print_banner: settings:proxyreload = 60
    MainProcess: MainThread: 1600865583: print_banner: settings:foreground = 0
    MainProcess: MainThread: 1600865583: print_banner: settings:log = 1
    MainProcess: MainThread: 1600865583: print_banner: settings:debug = 1
    MainProcess: MainThread: 1600865583: print_banner: settings:username = username
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_0: 1600865596: do_CONNECT: Entering
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_0: 1600865596: do_transaction: Entering
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_0: 1600865596: get_destination: repo.anaconda.com:443
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_0: 1600865596: do_socket_connect: New connection: ('proxy', 8081)
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: MainThread: 1600865596: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_0: 1600865596: do_proxy_type: Searching proxy type
    MainProcess: Thread_0: 1600865596: do_socket: Entering
    MainProcess: Thread_0: 1600865596: do_socket: CONNECT repo.anaconda.com:443 HTTP/1.0
    MainProcess: Thread_0: 1600865596: do_socket: Sending extra b'Proxy-Connection: keep-alive'
    MainProcess: Thread_0: 1600865596: do_socket: Reading response code
    MainProcess: Thread_0: 1600865596: do_socket: Response code: 407 True
    MainProcess: Thread_0: 1600865596: do_socket: Reading response headers
    MainProcess: Thread_0: 1600865596: do_socket: Received Date: Wed, 23 Sep 2020 12:53:16 GMT
    MainProcess: Thread_0: 1600865596: do_socket: Received Content-Type: text/html
    MainProcess: Thread_0: 1600865596: do_socket: Received Cache-Control: no-cache
    MainProcess: Thread_0: 1600865596: do_socket: Received Content-Length: 2473
    MainProcess: Thread_0: 1600865596: do_socket: Received X-Frame-Options: deny
    MainProcess: Thread_0: 1600865596: do_socket: Received Proxy-Connection: Keep-Alive
    MainProcess: Thread_0: 1600865596: do_socket: Received Proxy-Authenticate: sanitized (9)
    MainProcess: Thread_0: 1600865596: do_socket: Received Proxy-Authenticate: sanitized (4)
    MainProcess: Thread_0: 1600865596: do_socket: Received Proxy-Authenticate: sanitized (20)
    MainProcess: Thread_0: 1600865596: do_proxy_type: Auth mechanisms: Negotiate NTLM Basic realm="###"
    genotrance
    @genotrance
    Didn't receive the full logs, can you open an issue
    Jeronim Morina
    @plattenschieber
    You'll find the issue here: genotrance/px#114
    datadu-de
    @datadu-de
    Hi guys, any way to start px "quietly" at startup? i.e. without cmd-window open all time?
    ok, found the issue genotrance/px#72 will follow the discussion there
    ksimonova
    @ksimonova

    Hello. I've followed the setup using px zip, I saved the config in an ini file and run the install function. I can install packages via cmd, however if i try to do the same through Jupyter Notebook via my Anaconda i get proxy error. What's wrong here?

    WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 502 OK'))'

    genotrance
    @genotrance
    I've never tried that
    Are too trying to get jupyter up work thru px
    Alejandro Villegas
    @showi92
    Hello. I need to know how to config px.exe using kerberos and a PAC file. The ini file is configured :

    [proxy]
    server =
    pac = http://wpads/proxy.pac
    port = 3128
    listen = 127.0.0.1
    allow = ...
    gateway = 0
    hostonly = 0
    noproxy =
    useragent =
    username =
    auth = kerberos

    [settings]
    workers = 2
    threads = 5
    idle = 30
    socktimeout = 20.0
    proxyreload = 60
    foreground = 0
    log = 0

    However I can't connect trough the proxy. This is the output:

    D:\PERSONAL\Python\px-v0.4.0\px-v0.4.0>px.exe
    Serving at 127.0.0.1:3128 proc MainProcess
    Serving at 127.0.0.1:3128 proc Process-1
    Alejandro Villegas
    @showi92
    In other console this is the output:
    C:\Windows\system32>pip install psutil
    WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))': /simple/psutil/
    WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))': /simple/psutil/
    WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))': /simple/psutil/
    WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))': /simple/psutil/
    WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))': /simple/psutil/
    ERROR: Could not find a version that satisfies the requirement psutil (from versions: none)
    ERROR: No matching distribution found for psutil
    genotrance
    @genotrance
    is pip configured to use this proxy?
    also, turn on your px logging to see what it says
    Alejandro Villegas
    @showi92
    @genotrance Ok. this is my output log when I'm trying to use curl with proxy parameters. I'm using the files from the latest release Px for Windows(Sept 4th,2018) with px.exe (latest pre-release) and px.ini from master branch
    Serving at 127.0.0.1:3128 proc MainProcess
    MainProcess: MainThread: 1607523994: detach_console: Freed console successfully
    MainProcess: MainThread: 1607523994: print_banner: proxy:server =
    MainProcess: MainThread: 1607523995: print_banner: proxy:pac = http://wpads/proxy.pac
    MainProcess: MainThread: 1607523995: print_banner: proxy:port = 3128
    MainProcess: MainThread: 1607523995: print_banner: proxy:listen = 127.0.0.1
    MainProcess: MainThread: 1607523995: print_banner: proxy:allow = ...
    MainProcess: MainThread: 1607523995: print_banner: proxy:gateway = 0
    MainProcess: MainThread: 1607523995: print_banner: proxy:hostonly = 0
    MainProcess: MainThread: 1607523995: print_banner: proxy:noproxy =
    MainProcess: MainThread: 1607523995: print_banner: proxy:useragent =
    MainProcess: MainThread: 1607523995: print_banner: proxy:username =
    MainProcess: MainThread: 1607523995: print_banner: proxy:auth = kerberos
    MainProcess: MainThread: 1607523995: print_banner: settings:workers = 2
    MainProcess: MainThread: 1607523996: print_banner: settings:threads = 5
    MainProcess: MainThread: 1607523996: print_banner: settings:idle = 30
    MainProcess: MainThread: 1607523996: print_banner: settings:socktimeout = 20.0
    MainProcess: MainThread: 1607523996: print_banner: settings:proxyreload = 60
    MainProcess: MainThread: 1607523996: print_banner: settings:foreground = 0
    MainProcess: MainThread: 1607523996: print_banner: settings:log = 1
    MainProcess: MainThread: 1607524062: verify_request: Client address: 127.0.0.1
    MainProcess: Thread_2: 1607526182: do_GET: Entering
    MainProcess: Thread_2: 1607526182: do_GET: Path = http://www.ecured.cu/
    MainProcess: Thread_2: 1607526182: do_transaction: Entering
    MainProcess: Thread_2: 1607526182: get_destination: www.ecured.cu:80
    MainProcess: Thread_2: 1607526182: find_proxy_for_url: Proxy found: mycompany.domain:8080
    MainProcess: Thread_2: 1607526182: get_destination: Proxy from PAC = mycompany.domain:8080
    MainProcess: Thread_2: 1607526182: do_socket_connect: New connection: ('mycompany.domain', 8080)
    MainProcess: Thread_2: 1607526182: get_response_wkb: winkerberos SSPI
    MainProcess: Thread_2: 1607526182: fwd_data: Reading response data
    MainProcess: Thread_2: 1607526182: do_socket: Entering
    MainProcess: Thread_2: 1607526183: do_socket: GET http://www.ecured.cu/ HTTP/1.1
    MainProcess: Thread_2: 1607526183: do_socket: Sending Host: www.ecured.cu
    MainProcess: Thread_2: 1607526183: do_socket: Sending User-Agent: curl/7.55.1
    MainProcess: Thread_2: 1607526183: do_socket: Sending Accept: /
    MainProcess: Thread_2: 1607526183: do_socket: Sending Proxy-Connection: Keep-Alive
    MainProcess: Thread_2: 1607526183: do_socket: Sending extra Proxy-Auproxy1_from_pacization: sanitized len(2421)
    MainProcess: Thread_2: 1607526183: do_socket: Sending extra b'Connection: Keep-Alive'
    MainProcess: Thread_2: 1607526183: do_socket: Reading response code
    MainProcess: Thread_2: 1607526183: do_socket: Response code: 407 True
    MainProcess: Thread_2: 1607526183: do_socket: Reading response headers
    MainProcess: Thread_2: 1607526183: do_socket: Received Server: squid/3.5.23
    MainProcess: Thread_2: 1607526183: do_socket: Received Mime-Version: 1.0
    MainProcess: Thread_2: 1607526183: do_socket: Received Date: Wed, 09 Dec 2020 15:02:55 GMT
    MainProcess: Thread_2: 1607526183: do_socket: Received Content-Type: text/html;charset=utf-8
    MainProcess: Thread_2: 1607526183: do_socket: Received Content-Length: 6140
    MainProcess: Thread_2: 1607526183: do_socket: Received X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
    MainProcess: Thread_2: 1607526183: do_socket: Received Vary: Accept-Language
    MainProcess: Thread_2: 1607526183: do_socket: Received Content-Language: en
    MainProcess: Thread_2: 1607526183: do_socket: Received Proxy-Authenticate: sanitized (9)
    MainProcess: Thread_2: 1607526183: do_socket: Received X-Cache: MISS from proxy1_from_pac
    MainProcess: Thread_2: 1607526183: do_socket: Received X-Cache-Lookup: NONE from proxy1_from_pac:3128
    MainProcess: Thread_2: 1607526183: do_socket: Received Via: 1.1 proxy1_from_pac (squid/3.5.23)
    MainProcess: Thread_2: 1607526183: do_socket:
    MainProcess: Thread_2: 1607526183: do_socket: Received Connection: close
    MainProcess: Thread_2: 1607526183: do_transaction: Auth required
    MainProcess: Thread_2: 1607526183: do_transaction: Didn't get challenge, auth didn't work
    MainProcess: Thread_2: 1607526183: do_GET: Error 407
    MainProcess: Thread_2: 1607526183: fwd_resp: Entering
    MainProcess: Thread_2: 1607526184: log_message: "GET http://www.ecured.cu/ HTTP/1.1" 407 -
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Server: squid/3.5.23
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Mime-Version: 1.0
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Date: Wed, 09 Dec 2020 15:02:55 GMT
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Content-Type: text/html;charset=utf-8
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Content-Length: 6140
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Vary: Accept-Language
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Content-Language: en
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Proxy-Authenticate: Negotiate
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning X-Cache: MISS from proxy1_from_pac
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning X-Cache-Lookup: NONE from proxy1_from_pac:3128
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Via: 1.1 proxy1_from_pac (squid/3.5.23)
    MainProcess: Thread_2: 1607526184: fwd_resp: Returning Connection: close
    MainProcess: Thread_2: 1607526184: fwd_data: Reading response data
    MainProcess: Thread_2: 1607526184: fwd_data: Content length 6140
    MainProcess: Thread_2: 1607526184: fwd_data: Close proxy connection per header
    MainProcess: Thread_2: 1607526184: fwd_resp: Done
    MainProcess: Thread_2: 1607526184: do_GET: Done
    genotrance
    @genotrance
    Avoid setting proxy:auth in the ini file and try again
    It should be auto detecting
    Alejandro Villegas
    @showi92
    Excellent!!, this was the solution. I installed Django framework using pip --proxy=http://127.0.0.1:3128 install Django and everything works fine. All dependencies were downloaded . Thank you very much.
    genotrance
    @genotrance
    Cool!
    baarbeh
    @baarbeh
    Hi Genotrance, thank you for this project! What is the preferred method for updating from stable to the latest release? I installed px using the stable 0.4.0 binaries. Can I drop px.exe from the vHead release into the folder or should I use another method to re-install (e.g. using pip or from source)? Thank you again!
    genotrance
    @genotrance
    @baarbeh - yes that should work