Skip to main content
We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.
Unix & Linux

Return to Question

punctuation
Source Link
ctrl-alt-delor
ctrl-alt-delor
  • 28.8k
  • 11
  • 66
  • 113

I'm using ParrotSec (Debian based) and installed Google Chrome recently. Unlike Firefox, Google Chrome doesn't have an option to set a proxy in the UI instead it uses system proxy. In my case, I wanted it to work with Burp Suite and need Chrome traffic to go through the proxy http://127.0.0.1:8080.

I tried the following commands on terminal. Each one opens Chrome, but the proxy doesn't work. Chrome is directly connecting to internet.

google-chrome --proxy-server="https://127.0.0.1:8080"
google-chrome --proxy-server="https=127.0.0.1:8080"
google-chrome --proxy-server="http://127.0.0.1:8080"
google-chrome --proxy-server="http=127.0.0.1:8080"

None of them worked. Proxy is working perfectly in Firefox, but not in Chrome. Any idea what's happening?

Additional info: I'm using the OVA downloaded from ParrotSec in Virtual Box and the desktop environment is mate 1.24.0. I verified the --proxy-server flag exist by typing man google-chrome-stable

I'm using ParrotSec (Debian based) and installed Google Chrome recently. Unlike Firefox, Google Chrome doesn't have an option to set a proxy in the UI instead it uses system proxy. In my case, I wanted it to work with Burp Suite and need Chrome traffic to go through the proxy http://127.0.0.1:8080.

I tried the following commands on terminal. Each one opens Chrome but the proxy doesn't work. Chrome is directly connecting to internet.

google-chrome --proxy-server="https://127.0.0.1:8080"
google-chrome --proxy-server="https=127.0.0.1:8080"
google-chrome --proxy-server="http://127.0.0.1:8080"
google-chrome --proxy-server="http=127.0.0.1:8080"

None of them worked. Proxy is working perfectly in Firefox but not in Chrome. Any idea what's happening?

Additional info: I'm using the OVA downloaded from ParrotSec in Virtual Box and the desktop environment is mate 1.24.0. I verified the --proxy-server flag exist by typing man google-chrome-stable

I'm using ParrotSec (Debian based) and installed Google Chrome recently. Unlike Firefox, Google Chrome doesn't have an option to set a proxy in the UI instead it uses system proxy. In my case, I wanted it to work with Burp Suite and need Chrome traffic to go through the proxy http://127.0.0.1:8080.

I tried the following commands on terminal. Each one opens Chrome, but the proxy doesn't work. Chrome is directly connecting to internet.

google-chrome --proxy-server="https://127.0.0.1:8080"
google-chrome --proxy-server="https=127.0.0.1:8080"
google-chrome --proxy-server="http://127.0.0.1:8080"
google-chrome --proxy-server="http=127.0.0.1:8080"

None of them worked. Proxy is working perfectly in Firefox, but not in Chrome. Any idea what's happening?

Additional info: I'm using the OVA downloaded from ParrotSec in Virtual Box and the desktop environment is mate 1.24.0. I verified the --proxy-server flag exist by typing man google-chrome-stable

Source Link
Sagar V
Sagar V
  • 131
  • 3

Google chrome connect directly to Internet even when opened with proxy

I'm using ParrotSec (Debian based) and installed Google Chrome recently. Unlike Firefox, Google Chrome doesn't have an option to set a proxy in the UI instead it uses system proxy. In my case, I wanted it to work with Burp Suite and need Chrome traffic to go through the proxy http://127.0.0.1:8080.

I tried the following commands on terminal. Each one opens Chrome but the proxy doesn't work. Chrome is directly connecting to internet.

google-chrome --proxy-server="https://127.0.0.1:8080"
google-chrome --proxy-server="https=127.0.0.1:8080"
google-chrome --proxy-server="http://127.0.0.1:8080"
google-chrome --proxy-server="http=127.0.0.1:8080"

None of them worked. Proxy is working perfectly in Firefox but not in Chrome. Any idea what's happening?

Additional info: I'm using the OVA downloaded from ParrotSec in Virtual Box and the desktop environment is mate 1.24.0. I verified the --proxy-server flag exist by typing man google-chrome-stable