I have an Asustor NAS connected to my router, on a Mac Studio. The router shows the unit as connected, with IP address 192.168.0.102.
If I open that URL in my Chrome browser, I get a page that says 'This site can't be reached. 192.168.0.102 refused to connect.' This happens if I use port 8000 (http) or 8001 (https).
I can connect to the NAS with Finder, and see the data stored on it, so the device is connected and responding, but I cannot connect to the OS (called ADM) through the browser.
Does anyone have any idea what could be the issue here?
You are not going to believe this. When Chrome says the site can't be reached, all you have to do is enter the text 'thisisunsafe' anywhere in the browser window. This bypasses the Chrome security features.
See https://cybercafe.dev/thisisunsafe-bypassing-chrome-security-warnings/
Related
I wanted to change DNS server on macOS 10.14.6 by going to System Preferences -> Network -> Advanced..., and adding 8.8.8.8 in the DNS tab. Since then, Chrome gives me a
DNS_PROBE_FINISHED_BAD_SECURE_CONFIG error.
First I returned to the previous DNS settings (putting 192.168.1.1 in place of 8.8.8.8). Since then I tried switching my router off/on. I cleared the Chrome DNS cache as explained in this answer. I cleared browsing data (history, cache, cookies) on Chrome. I stopped and restarted the mDNSResponder service.
From the terminal, both ping and curl work fine. Other browsers (Safari) work fine. Why do I see this error, and how do I solve it?
If you have checked all DNS settings but still got this error, you could take a look at the Chrome Secure DNS to see if this setting had switched on.
To turn Chrome Secure DNS on or off:
Open Chrome.
At the top right, tap More and then Settings.
Under “Privacy and security,” tap Security.
Turn Use Secure DNS on or off.
Background: I have a web app that is accessed via Chrome on a Windows 10 machine.
I also have a native Win10 application installed on the device. The web app sends data to the Win10 application via a local web service running on the machine in IISExpress.
To allow for HTTPS communication on port 44300, I've created a self-signed certificate via PowerShell:
New-SelfSignedCertificate -DnsName "localhost" -CertStoreLocation "cert:\LocalMachine\My" -NotAfter (Get-Date).AddMonths(60)
And then imported it to 'Local Computer\Trusted Root Certificates\Certificates'
From within the web app I send a command to the win10 app that looks something like this:
https://localhost:44300/CMTService.svc/JumpToAssignment?Param=Key=418584577
The win10 app is polling for these requests and picks up the message.
Issue:
Different versions of Chrome behave differently with the acceptance of the self-signed certificate. For instance versions 62, 64 and 75 all accept the certificate and allow for communication with the web service. But other versions of Chrome like 76 and 78 block communication. The Security tab in the Chrome DevTools shows https://localhost:44300 as "Unknown / cancelled" and my requests fail with ERR_SSL_CLIENT_AUTH_CERT_NEEDED. Whereas in working versions of Chrome my URL shows under "Secure origins". The only thing that I change is the Chrome version to get these different results.
I've tried enabling the Chrome setting to allow for invalid certs for localhost (chrome://flags/#allow-insecure-localhost). This temporarily works, but then after closing and reopening chrome, my requests start failing again with the same error code.
If I take one of my failing URLs and paste it into a new Chrome tab, suddenly communication with my native app in my web app resumes as normal. But it only works for that session - when I close and reopen Chrome my communication is broken again.
Question:
How do I allow for communication between my Chrome v78 web app and my local native app?
ERR_SSL_CLIENT_AUTH_CERT_NEEDED means the server is asking the browser for a certificate for client authentication.
You've described how you setup server authentication, but not described how you setup client authentication.
Likely you have enabled certificates for client authentication, but have not configured the web app to send the correct client certificate or have not configured the native app to accept the correct client certificate. That's a very open ended topic to be prescriptive without knowing more about your development efforts, but you can confirm if client authentication is enabled by inspecting a packet capture. One description of the handshake is here : https://blogs.technet.microsoft.com/nettracer/2013/12/30/how-it-works-on-the-wire-iis-http-client-certificate-authentication/.
Just an update: I implemented a javascript workaround to get around my communication issues. When first loading the web app, I simply send my first communication to IIS (destined for Win10 native app) in a separate chrome browser tab. For whatever reason this allows for successful acceptance of the certificate and kick starts the communication with IIS. This is my code to send the command in a new tab and then close it:
var inst = window.open(launchWinAppURL);
if (inst != null) {
window.setTimeout(function() {
inst.close();
}, 1000);
}
This is not the most elegant solution, but it seems to work on all chrome versions, so i'm satisfied.
Is the web app only communicating with the one win10 machine? Have you installed the self-signed cert directly to the machine? I would try installing it directly to the machine and see if the later instances of chrome allow communication.
My work uses FortiClient for our VPN service. I can connect to our VPN just fine, and I can access my shared drive on one of our servers. However, when I try to launch Chrome and connect to any website I get this error.
The second I disconnect from the VPN, my Chrome pages will load again.
I have tried using my phone's hotspot as the Internet connection, and the VPN works fine while on the hotspot, including the Chrome pages loading. So I think it is something wrong with my router.
I have Spectrum/Time Warner Cable as my ISP, and when I called them, they said there's nothing they can do because my Internet connection technically is working.
Is there any kind of setting I can check in my router to see if it is blocking my work VPN? I have the Ubee router that was provided to me by TWC.
I spoke with the people at FortiClient and they had me manually change the DNS that the VPN was using to be Google's 8.8.8.8 address. Everything worked once I did that.
I am using "Oracle Database 10g Express Edition" and I am trying to start Database homepage but Google Chrome or Firefox are showing errors. Note: I am not using any proxy.The message shown in Chrome is
Google Chrome's connection attempt to 127.0.0.1 was rejected. The
website may be down, or your network may not be properly configured.
What are the possible solutions?
I had the same problem. I solved it as follows:
When opening Tomcat Application Manager from the shortcut on the Start menu, then it opened the link http://127.0.0.1:8080/manager/html which caused exactly the same error as you report
All I did was remove the :8080 from the URL and it worked
I am developing a website locally using wamp. The site uses ssl and works completely fine in firefox. In Google Chrome, I get an error:
https://example.local/ gives me this error
This webpage is not available
The connection to example.local was interrupted.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the wrench menu > Options > Under the Hood > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
http://example.local/ works fine in chrome.
I should note that in IE I get Internet Explorer cannot display the webpage error, but again, it works fine in firefox...
Any help?