My Chrome browser is in a weird state. It claims that it's configured to use a proxy server and that it can't connect to that server. Problem is, when I go to the LAN settings, the option to use a proxy server is deselected. Toggling this setting has no effect.
I've tried reinstalling Chrome but the problem persists.
Any idea on how I can get it to stop trying to use whatever proxy it thinks it's configured for?
try selecting no proxy in network settings of chrome. i'm not sure whether this going to work but it is worth trying. its not going to do any harm.
hope you find a solution
Related
On Linux Debian 10 (Buster), I am using the http(s) client google-chrome-stable.
I was configuring (nginx) and testing (chrome) a reverse proxy and it got cached using a wrong domain.
I fixed the configuration but it still resolve to the wrong domain.
I have tried to go chrome://net-internals/#dns and click on Clear host cache but that didn't change anything.
I have tried to go chrome://net-internals/#sockets and click on Flush socket pools but that didn't change anything.
I am not working with FireFox, so FireFox can resolve correctly (so does curl).
After about 10 minutes, without restarting chrome. I did F5 (refresh) and it was loading the proper page. I haven't found a manual way to immediatly clear chrome cache.
I am doing devops and I haven't solved this issue for years.
Would love to know how to do one day :O
What happens if you open developer console F12 and then hold down on the refresh button and then select empty cache and hard reload?
Take a look at this gif for an example.
I am learning to make chrome app which will receive UDP packets from remote device. All works perfectly fine, however, in order to receive packets from remote device I need to turn off windows firewall.
Now the problem is that I do not see a way to add this app to pass firewall exception. Because I only see option to allow Chrome through firewall, not any of its apps.
What is the solution / workaround to this problem?
Thanks
Since I didn't get any answer, the best possible solution I could find so far is to add the port on which my chrome app will listen to firewall inbound rules. I didn't know this was possible until i read this article https://www.thewindowsclub.com/block-open-port-windows-8-firewall
However I still don't consider it the right solution because lets say I publish my app online for other people, it will not be convenient for them to be adding rules to their firewalls.
I am sure there must be a better solution.
I need to access a IP restricted website. Since the IPs of my coworkers any my own one changes all the time I would like to use one of my root servers running Nginx as a Proxy in Chrome and Firefox.
Yet I don't know how to set up Nginx for that kind of usage. Googling is also difficult because the term proxy is used in a lot of different contexts.
Can I configure Nginx to act as a HTTP proxy to that page, if yes, how do I set it up?
Note: I can't use it as a reverse proxy to the page. It does work but all links on the page point to the original URL which I can't fix easily (at least I don't know how).
Chrome seems to have released an update over the past week. This has caused at least 50 of our internal applications to throw the exception shown below. The solutions I have researched over the Internet, talk about updating the application server with a stronger cipher. However, our applications are spread out over IIS, tomcat, jboss, weblogic and websphere. Its not practical to expect all of these application servers to be updated. Is there no way to get Chrome to allow an "exception" for these sites ? Since these sites are all internal, the security is not really a concern.
Apparently, Firefox throws the same exception but there is a documented fix for that (by changing some settings in Firefox). Is anyone aware of a similar fix in Chrome.
Error
Server has a weak ephemeral Diffie-Hellman public key
ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY
I found a temporary workaround that should disable the security check in Chrome that is causing that error. It goes without saying that you do NOT want to use this while browsing the open web.
Try adding the following command argument to Chrome when you start it up:
--cipher-suite-blacklist=0x0088,0x0087,0x0039,0x0038,0x0044,0x0045,0x0066,0x0032,0x0033,0x0016,0x0013
I found this solution at this google forum post. Hopefully it will help!
While Maximillian's workaround might work for you at the moment, there is no supported way to add an exception.
The only safe solution is to upgrade the servers, and a less fragile workaround might be to put better proxies right in front of some of the servers.
This problem I found because of the JDK version running on App Server.
If your weblogic/apache server running on java JRockit version "1.6.0_33" & "1.6.0_45" or below you will face this issue.
A solution is to upgrade java to higher version like "1.6.0_101" and higher and restart app server.
I've solved this problem without upgrading jrockit but configuring the ssl section like this
<ssl>
<enabled>true</enabled>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>false</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
<jsse-enabled>true</jsse-enabled>
</ssl>
Can't tell you exactly whats makes the difference but it solved many different problems on SSL with chrome
I am working on Mac and have identical Proxy settings for the System and Firefox browser. However, I am able to see my Firefox traffic in Chrales but I don't see my Chrome and Safari traffic (which use System Proxy Settings). What do I need to do? How can I check the debug this?
Already restarted my browser but it didn't help. I have set and reset proxy settings, but of no use.
One thing to note: I am on a VPN although I don't think this should affect Chrome as Firefox is going through the proxy.
For anyone else using VPN: Charles must be turned on before VPN. So quitting VPN after turning on Charles won't work either.
Also in my case VPN can't be turned on at all.
Did you enable "Proxy-> Mac OS X Proxy"?
Quit your VPN! I was confused almost one year and really upset, i cannot record on my mac.But today i quit my vpn(xx-net) it does works.
Just got caught out with this - the Hola VPN Chrome extension was managing Chrome's proxy settings so it wasn't using the system proxy.
Simply disabling the Hola extension got it working for me again.
I turn off a chrome proxy plugin and it works!
Chrome extension 'SwitchyOmega' can solve the "VPN and Charles cannot turn on at the same time" issue by configure the auto switch option:
Add Charles mode
Add VPN mode
auto switch configuration
Use auto switch mode in Chrome
Desktop applications that set system-wide proxy don't work really well with VPN. I struggled with Charles & Fiddler because I was under a VPN network and almost all the time I couldn't use any of the apps while on my company VPN So I googled for Web Proxy chrome extension and found Requestly.
I am using the Requestly Chrome extension and the chrome extension works well with VPN and it has all the features that Charles has.