[pinebear123]

Ping works fine (as seen below). I also added an entry to windows firewall to allow network access to q.exe. The issue must be with the proxy, I just want to see what q sees.

I looked in registry and AutoConfigURL for proxy is http://xyz/abc.pac. The pack file has the rules for proxying. I am guessing that might be an issue.

Pinging dy2kttecucxn3.cloudfront.net [13.249.90.90] with 32 bytes of data:
Reply from 13.249.90.90: bytes=32 time=13ms TTL=237
Reply from 13.249.90.90: bytes=32 time=12ms TTL=237
Reply from 13.249.90.90: bytes=32 time=12ms TTL=237
Reply from 13.249.90.90: bytes=32 time=12ms TTL=237

Ping statistics for 13.249.90.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

[pinebear123]

I read proxy’s pac file and figured out the right proxy to use. Using that as the HTTP_PROXY solved the problem. If there are issues with the connection on the start-up, the log is not created however.

Thank you

[pinebear123]

Is there a way to run q.exe with some verbose logging to see where the connectivity breaks? I tried setting http proxy via “set HTTP_PROXY=http://xyz:1080” and using -l option for logging, but the log file is not created.

[pinebear123]

Forgot to mention. I tried setting an environment variable HTTP_PROXY=http://myproxy.com:8090 but that did not work. That’s the proxy I used for Python’s pip