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.
Related
I have an R script that uses Plotly Dash to create a web page. I am running the script on a VM instance in GCP which is a Ubuntu server without GUI. When the script is executed, it says,
start 127.0.0.1:8050
My question is how to access this web page on a browser from anywhere. Since the VM doesnt have a gui/browser I cannot even test my web page..
Anyone could explain what I am missing here or any way to deploy my web page and access from anywhere?
I am unsure how your application works, but that ending line shows that the server is running on localhost and on which port is it serving. So you may want to access from an external browser with the instance's ip address: like http:// xx.xxx.xx.xx:8050 and let's see if it works. Otherwise you may need to set up a Remote Desktop Setup through Chrome to enable a GUI interface on the VM.
Also remember to make sure that traffic is allowed on that port 8050 checking /creating the firewall rules
I encountered the same problem. You need to change the IP address on which the dash server is running to the internal IP address of your gcp VM instance. It usually starts with 10.xxx.x.x. You can find this internal address in the 'IP address' tab in the VPC networks section on the google cloud console. So do this:
app.run_server(host='10.xxx.x.x', port='8050')
Open a browser and browse to http://externalip:8050. Make sure you have your firewall rules set up correctly.
You should now be able to see the dash app.
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.
Using: Chrome 67.0.3396.99
Our webserver implements X.509 client authentication. The certificates are offered through the PKCS#11 interface; we connect a smartcard (in this case: Yubikey 4), the browser prompts for the certificate selection and PIN.
We disconnected the smartcard and visited the authenticated domain (say, localhost:8000) to observe the behavior of the webserver (in a local development environment).
The webserver correctly refused to serve the request.
However, Chrome now does never send anymore the certificates while visiting localhost:8000, even if the smartcard is connected.
The following did not resolve the problem:
Clearing all site data through the developer console;
Resettting site preferences to their defaults (through chrome://settings/content/siteDetails?);
Rebuilding the webserver.
Any pointer where I can clear this state from Chrome would be greatly appreciated. As a temporary fix, we run the server at a different port but this is not an option on the long term. As this scenario is very plausible to also happen in production.
Good Morning. I have downloaded and installed GE Enterprise portal v5. When I start the application, it automatically launches the browser and sends me to http://localhost:9335. It loads just fine and I am able to view the image and polygon. I then close the server and open the portable.cfg and added the following line: accept_all_requests True, which us supposed to allow others to view and use the published globes and services from other machines. I then restart the application. When I try and navigate to my portal instance via another machine or via the named machine name http://9335 I get page not found. I have tried changing the ports, disabling my local firewall and HIPs with no luck. Are you supposed to be able to hit an instance of portal from a url other than localhost?
Thanks.
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.