I am trying to run google chrome with a proxy server on my Ubuntu environment and cannot get this working. Here is my command:
google-chrome --proxy-server="http://111.111.111.111:111"
I can connect using this same command on my local (mac) machine, whatismyip.org shows the ip address of the proxy and everything is dandy. On the Ubuntu server, I simply get a timeout. I have tried several different proxies and cannot get this working.
Is there a default security setting on a fresh ubuntu install that would prevent me from being able to do this?
Thanks!
Looks like my proxy was blocking my server IP. Ubuntu is fine, carry on.
Check your proxy, because command is working.
google-chrome --proxy-server="http://xxxxx:port"
Related
I'm trying to decrypt HTTPS using Wireshark on Ubuntu 20.04.
I use this guide.
Basically:
You install Wireshark
You add SSLKEYLOGFILE environment variable
You open Chrome and visit the HTTPS site
You import the ssl key log file into Wireshark
And it decrypts the traffic
But no matter what I do, my .ssl-key.log file is empty. I closed Chrome and reopened it. Visited https://google.com and nothing is written in that file. I even restarted my laptop.
And these questions did not solve my problem:
Chrome not Firefox are not dumping to SSLKEYLOGFILE variable
SSLKEYLOGFILE environment variable doesn't populate any text file
I use chrome(Version 97.0.4692.99 (Official Build) (64-bit)) is worked.
you should run killall chrome to kill all chrome background instance.
then rerun google-chrome is work.
OR
user fiddler decrypt HTTPS,
https://docs.telerik.com/fiddler/configure-fiddler/tasks/decrypthttps
Decrypt HTTPS traffic with Wireshark and Fiddler
https://www.hhutzler.de/blog/decrypt-https-traffic-wireshark-fiddler/
The problem may be that Google Chrome doesn't have access to your user environment.
To resolve this,
launch google-chrome directly from a user terminal whenever you want to decrypt new traffic
or make a psueo-google-chrome launcher that points to the real google-chrome after setting the SSLKEYLOGFILE env variable
Recently I installed Gatling for performance testing on Ubuntu 14.04. And to run the recorder I needed to configure a proxy server in my browser. I tried to change proxy settings in Google chrome, but I don`t have rights. So I tried to do it using network settings in Ubuntu (Network -> Network proxy). But when I open a website which I need to test, nothing happens in the recorder.
So I do not really know is there a problem with the proxy server or Gatling itself? And how to check if the proxy server is configured correctly?
I would appreciate any help!
It's a bit too late, but I had a similar problem today. Was able to solve only by setting global IP address like xxx.xxx.xxx.xxx. Nor localhost nor 127.0.0.1 worked for me Chrome. After that I was able to notice http requests in Recorder inside Executed Events
Hopefully it could help somebody else
Edit : this is how setting looks like in Chrome, taking into account you have specified in Recorder Listening port to be 8000 also:
I am developing a webpage that uses camera. When I test in Chrome in my local network, camera doesn't work and I get warning in the console:
getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See link for more details.
In the link provided there is an instruction to set some flags in Chrome. So I tried. My command looks like this:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --unsafely-treat-insecure-origin-as-secure="192.168.0.15" --user-data-dir=c:\chrome-dev-profile
But when I run Chrome I get this message:
You are using an unsupported command-line flag: --unsafely-treat-insecure-origin-as-secure. Stability and security will suffer.
What am I doing wrong?
Is there another way I can test in local network without setting up https server? I need this just for development.
Luka,
I've run into this bug just yesterday. I have not found out how to get Chrome to honor that flag on the command line yet. But I did find a workaround that works for my case.
I'm running my web services on a Linux machine that is running an ssh server. I'm testing on windows with chrome, and used putty to connect to the linux box from windows and then created a "local port forward" to make my remote linux box's ipaddress:port appear on localhost:port on windows. Depending on your platform this workaround may work for you. This approach isn't too cumbersome if you only have a few ports to forward.
In my particular case my setting for putty looked like
L8080 localhost:8080
To see more about port forwarding and ssh see: https://help.ubuntu.com/community/SSH/OpenSSH/PortForwarding
Just updated MAMP to version 3.2.1 on Yosemite. Both Apache and MySQL servers are green but when I go to my localhost I keep getting: This webpage is not available ERR_NAME_NOT_RESOLVED in browser (Chrome). I’ve tried incognito browsing and Firefox with the same result, tried both the MAMP default port settings and ports 80 & 3306, tried a reinstall of MAMP and rolling back to previous install of MAMP; all without success.
Can anyone suggest how to fix this…it’s starting to drive me crazy!
Possible Thoughts;
In your /Applications/MAMP/htdocs/ folder, is there something in there for your browser to load? Some sort of index.html or index.php file? Could it have gotten removed accidentally?
When you launch MAMP and go to Preferences -> Ports, what is the Apache port? You mentioned you tried the default (8888/8889) and 80/3306, but could the port number somehow have gotten changed?
Is there any chance that some other Apache service is running? This is unlikely as you mentioned that MAMP shows Apache status as green, but it could be worth stopping MAMP, opening Terminal and doing sudo apachectl stop, returning to MAMP and changing the ports to 80/3306, then returning to Terminal and doing sudo apachectl restart. Then return to MAMP and start services again.
If none of the above work, what if you set the Apache port in MAMP's preferences to something random, like 8712, and then try http://localhost:8712/ to see if it loads.
Let us know if you've tried those already!
Had a similar issue. If 127.0.0.1 is working then you just need to point localhost to 127.0.0.1. Edit /etc/hosts file (requires sudo) and include
127.0.0.1 localhost
That resolved it for me.
This still happens occasionally when updating macOS.
Going through all local Wordpress sites and changing the dev url isn't ideal, though necessary when changing the port.
What rather solved the issue for me was restarting Apache as suggested by #ZbadhabitZ, keeping original port number:
sudo apachectl restart
I had this issue because I had Docker Desktop running at the same time; I shut this down and it started working so it must have been a port conflict.
EDIT:
The localhost seem to be working fine in my firefox, IE and even Chrome's incognito mode. These is a problem specific to chrome. Any ideas?
PREVIOUS:
I just uninstalled VisualSVN Server from my Windows 7. But now when I try to hit localhost, I get redirected to localhost/svn. I am using WAMP and developing something that requires the root access. I can not put the project in a sub directory. I have also tried netstat -ao but no process is using ports 80 or 443.
You may have solved the problem....but for future, those who came here like me looking for a solution to this, this seems to be a prob for browser cache....clearing browser cache history solves the problem.....did for me...
If you uninstalled VisualSVN Server, then it's some other application which runs on 80 / 443 port that redirects you to /svn. Some steps that may help you to determine the root cause:
Verify that VisualSVN Server has been successfully uninstalled.
Start appwiz.cpl and see whether VisualSVN Server is listed as the installed application,
Start services.msc and see whether "VisualSVN Server" service is listed.
Run netstat -anbv and see which app runs on HTTP(S) port.