Note: this affects firefox only.

I have a simple proxy profile that specifies "SOCKS5". Every time I open firefox, the connections get proxied through socks4a, which gets stuck because my SOCKS server (dante) doesn't support SOCKS4a. Beyond the symptoms of not being able to access anything, I can see on the SOCKS server that firefox attempts to connect to IP address 0.0.0.1, which is a clear SOCKS4a-specific thing (as specified by https://www.openssh.com/txt/socks4a.protocol )

Every time I open firefox I have to manually change my profile setting to socks4 and back to socks5 again, and everything starts working again. Alternatively I can also simply switch to the "direct" profile and switch back to the proxy profile.

I'm not sure if this is a ZeroOmega bug, or if this because of Firefox. I am also using ZeroOmega in Google Chrome (with the same SOCKS server) and I do not have this issue.

I'm using:

• Firefox 137.0 on Windows 11 23H2
• ZeroOmega 3.3.23