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.
Related
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/
I have little experience with DNS and its related systems. I have a business website running on a server at my house, and as a side project setup a local DNS cache and zone that allows me to connect locally using my remote domain name. Bind9 on ubuntu.
It works. On Iphone safari, there are no issues. Using the domain to connect samba shares has had no issues. But on my computer google has some issues. After immediately opening chrome everything works, and I can access the site. However after a minute and for no apparent reason I can no longer connect.
Is google chrome switching to another DNS server? Can I change this in settings? Google chrome settings has an option relating to secure DNS. Does this not allow it to connect to a DNS server that doesn't have some encryption? Thanks.
I am hosting my page inside the sdcard of arduino, I have implemented web speech api feature in that, however when I test my site using 127.0.0.1/project-X , everything works perfect, but when I use 192.168.1.4(which is same machine) or 192.168.1.10 (which is other laptop having WAMP) Chrome does not allow the microphone? I have also tried to start Chrome using different flags found on Google but none of them worked. What to do? I just want Chrome to allow using microphone from local ip also!
Chrome now allows Microphone access over secured Http only. You can very easily create your own signed SSL certificate and use that to host your page via Https.In tomcat server.xml you just have to un-comment the ssl connector and point to the location of your certificate.
I am developing an application that uses WebRTC and I want Chrome to use the system camera. From what I understand, the use of the camera is allowed (in the latest versions of Chrome) only from "secure locations" (https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins), like localhost and 127.0.0.1.
I want to test it locally and connect to the server both from a client that resides on the same pc as the server, and from a client from another pc. In particular, the client that connects from another pc needs to connect to the server using its IP address (I am developing/testing it in an Intranet), but the client cannot use the camera because it is not calling localhost.
Is there a way to disable this constraint, so that I am able to test it in an Intranet?
If not, are there any alternatives?
try the unsafely-treat-insecure-origin-as-secure flag in Chrome:
http://peter.sh/experiments/chromium-command-line-switches/#unsafely-treat-insecure-origin-as-secure
I'm having a strange problem with a separately hosted subdomain I have. I'm running an application on Engine Yard, let's call it mysite.com. I have a wildcard SSL certificate installed there which covers all the subdomains (things like api.mysite.com). We recently decided to migrate our blog to be hosted independently (right now it lives on wordpress.com). Because I can't run the blog alongside our Rails app with ease on Engine Yard, I decided to grab some cheap hosting space from Dreamhost to host our Wordpress blog there. I set up the server there to fully host our subdomain (let's call it blog.mysite.com), and updated the DNS A record on Hover (our DNS provider) to point blog.mysite.com to the Dreamhost server. So here's the issue:
If I go to blog.mysite.com via Firefox or Safari on my Mac I see the basic Wordpress install which I set up. However, if I try to view things with Chrome I get the following error:
This webpage is not available
Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out.
This happens on all Macs running Chrome I could get my hands on. I tried both clearing the cache and flushing the DNS but nothing. The weirdest part is Chrome keeps looking for https://blog.mysite.com instead of http://blog.mysite.com. There is no SSL cert installed on the subdomain for the blog on Dreamhost because it's not necessary.
Has anyone ever come across this before? And in case anyone wants to try the actual address is http://blog.frestyl.com.
sounds like you have a 301 permanent redirect that Chrome registered http://blog.frestyl.com -> https://blog.frestyl.com. Besides clearing the cache I'm not sure what else can be done.