Issues with Amazon Q CLI on WSL Behind Corporate Proxy

[felipemacedo1]

Hello everyone, I hope you're doing well!

I’ve been running some tests with the Amazon Q CLI on Windows 11 using WSL with Ubuntu behind a corporate proxy. I made significant progress by setting up a bridge to bypass the proxy via Windows. However, recently I started encountering some issues. It’s possible that WSL or Windows assigned a new IP, which might have broken my bridge.

When I run the Amazon CLI, I get the following error:

Amazon Q is having trouble responding right now:
   0: Failed to send the request: An unknown error occurred: request has timed out
   1: An unknown error occurred: request has timed out
   2: request has timed out
   3: request has timed out
   4: operation timeout (all attempts including retries) occurred after 30ms

Location:
   crates/chat-cli/src/cli/chat/mod.rs:1146

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

I would really like to read these logs to understand what’s happening, but I haven’t been able to find them (maybe they’re inside WSL, but I’m not sure of the correct directory).

I don’t have much experience with WSL, so I’d like to know if anyone has encountered this before or has any suggestions that could help.