search

genotrance / px

An HTTP proxy server to automatically authenticate through an NTLM proxy
MIT License
955 stars 99 forks source link

px 0.8.4: PAC configuration seems to cause unstable behaviour #198

Closed pauko closed 8 months ago

pauko commented 1 year ago

Hello community!

I'm using px version 0.8.4. on a Windows host with hostonly and gateway options, as I want processes running in WSL2 to use that local proxy to communicate with "the outer world" via the corporate proxy server. Additionally, i set the URL of the PAC file in the pac field of px.ini.

I see considerable stability issues with this setup. Out of a sudden, the px processes on Windows terminate without any visible indication of a crash, neither on the command line nor in the log files, which I let it write with log=1 in px.ini. It's quite reproducible when running some npm install ... inside WSL2.

However, if I give the URL of the corporate proxy in the server field instead of the PAC file in pac, px seems to run smoothly.

Additional information, maybe relevant: I have to run wsl-vpnkit in the standalone script setup with "autostart by systemd" inside the WSL2 distribution.

As said above, I don't find any error messages or crash dumps in the log files, but maybe px leaves some interesting information somewhere else. If somebody tells me, how to retrieve such information (if existing), I can append it to this report!

Torsten4BoschBTHildesheim commented 9 months ago

Same with px 0.9 (windows)

But maybe I have some more debug info. I get the following message in the command line window:

Assertion failed: !runtime_data->thread_state, file module.c, line 83

genotrance commented 9 months ago

Looks like this is basically a duplicate of #206. Thanks for the reports - I'll figure this out for v0.9.1.

genotrance commented 8 months ago

Fixed in v091.

genotrance commented 8 months ago

v0.9.1 has been released.