My github pages site with a custom domain works just fine on mobile but when i try to access the same URL from desktop i get a DNS_PROBE_FINISHED_NXDOMAIN error. Any ideas why this may be ? The site can be found here if it helps Site
EDIt: it works with this link which does not include 'www.' if this makes my problem any clearer
I doubt that it shows on your mobile, DNS records doesn't return anything WhatsMyDNS
Are you certain that you've got your DNS server up correctly.? I did a lookup for your domain name and it doesn't appear that you've got your CNAME pointing to GitHub pages. To do so, add a CNAME record to your domain via your domain registrar's dashboard. This should point to the name of your GitHub pages url (ex. john.github.io/xyz). You can read up on this more here.
I notice you say that it doesnt work if you add the www.. I'm not exactly sure why this is (there's not enough information to say why). I'm guessing you did not correctly set up the record, so here's what it should look like:
# A 4H 127.0.0.1
(You may change the TTL and IP, of course)
I'm guessing you forgot the # in the first field, which puts it under both www and the root subdomain. If this is not the case, you can attempt to fix this issue by adding www in a separate record to easily resolve the problem.
www A 4H 127.0.0.1
Note that this will work for both CNAME and A records.
Maybe desktop dns server is not so fast to fetch changes.
Change dns server in desktop connection settings for a public google's 8.8.8.8. For windows that's going to be Control Panel > Network and sharing center > Change adapter settings > Right click adapter (in my case it was WIFI) > Choose connection (Internet protocol Version 4) > Click Properties > Select "Use the following DNS server addresses" > Enter 8.8.8.8 in "Preferred DNS server" > Click OK
I am a newbie in the field and faced the same issue. Came here to find the solution. I just did plug out the ethernet and connected my laptop to my wifi and it worked.
Related
I'm getting the following error for one specific website (and only one specific website):
I've tried the following:
Making sure my time / data settings are correct
Clearing all browsing data
Deleting and reinstalling Chrome
Nothing works. Interestingly, I only get this error for one specific site (www.datacamp.com). And when I turn off wi-fi and tether my iPhone, I'm able to get through to the site. When I turn my wi-fi back on, I get errors again.
When I view details I see this:
And when I view the certificate I see this:
I've tried deleting the certificate, but I get the following message:
Any help is greatly appreciated!
If you are getting this error when access localhost, simply go to
chrome://flags/
and enable Allow invalid certificates for resources loaded from localhost.
Ok, I don't know why it took me so long to try this. I just unplugged my modem and router, then plugged them back in. At least for now, it seems to have resolved the issue...
Check your connection's DNS entries. It's likely a adware or malware program modified them.
open network and sharing center
On the left side- click on:
change advanced sharing settings.
click on home or work.
go through and check "turn off" for the first three questions.
turn on password.
Your computer connection was wide open!!!!
Flushing DNS worked for me in Windows 10. Simply open powershell and issue this command:
ipconfig /flushdns
Adding Google DNS 8.8.8.8 and the Cloudflare DNS 1.1.1.1 solved my issue.
If you are facing this while visiting a website, you can follow below.
This might not solve the issue always. But, this is how I solve it around 8/10 times.
To Resolve this on Chrome :
[Approach 1]
Just Click on Proceed to www.xyzxyz.com..(unsafe)
[Approach 2]
Go to : chrome://net-internals/#hsts
Suppose the site for which the error shown is : https://twitter.com/xxx/yyy....
In the "Delete Domain" option, Enter domain as "twitter.com".
Press Delete.
Reload the page you were trying to visit.
How can I disable chrome using address bar for google search?
I cant access localhost at 0.0.0.0:6000, because chrome thinks it's a google search and not an url
any ideas?
This may be because a url was added to your search history. Google is doing you a favor because that's what you did once before somehow.
Try clearing your history to see if this is the case.
I went to "Clear Browsing Data" in Settings > Advanced and I was able to enter a localhost url again.
Be sure you end the url with "/" symbol.
Try:
http://0.0.0.0:6000/
Instead of:
0.0.0.0:6000
SOLUTION For chrome version 62:
settings > advanced > Use a web service to help resolve navigation errors > OFF
Try
- turn off Search Suggestions
- under LAN settings, uncheck "use automatic configuration"
Do you get the same behavior with an incognito window?
Try this alternative: http://127.1.1.1:6000 or 127.1.1.1:6000 (without http).
A search through the web has revealed several different possible causes to this problem as well as solutions.
Causes:
this is malware
this is a chrome/browser issue
this is a misconfiguration of the httpd service
Solutions:
scan for malware, though probably not the issue.
update the host file, so that localhost points to 127.0.0.1
confirm your httpd service is accepting http:// requests through port 80, 8080, or some other port.
make sure the URL has the correct port .. http://localhost:8080
try appending different delimiting characters [ / ? # ] to the URL ...
localhost/Dir/
localhost/Dir?p=x
localhost/Dir#123
does it happen on a specific directory?
localhost/Dir .. works
localhost/Dir2 .. goes to search.
This suggests that the httpd service's configuration may need to be fixed. or that an .htaccess file is the cause. If these problems can be ruled out, then it's a browser issue.
remove the autocomplete entry from the browsers search/address bar
in most cases, type the url, using the arrow keys - highlight the offending entry, press [DELETE] or [SHIFT}+[DELETE].
does your browser support turning off autocomplete or searching from the address bar?
.. chrome .. Disable Predictive Text
.. firefox .. Disable Predictive Text
open the CLI and issue [ >wget localhost/dir ]. Observe what is returned on a working vs non working directory.
Follow up:
This issue is especially annoying when working with .htaccess files and browser redirect statements in PHP, ASP, nodeJS, and JSP which redirect the browser to a specific URL, but instead takes the user to a search page. If at all possible pre-pend http:// and post-pend a slash (/) after the URL in redirects.
http://localhost/dir/
And, YES ... it is annoying to have to add extra characters (as a work around) to get URLs to work right.
I might be a bit late to the party here but I just encountered this same problem on the current chrome (v. 96.0.4664.93) and could it would not resolve any local address using any of the other methods that I found on the web(http://192.168.178.1 or setting flags or insecure DNS).
What solved the problem, was a simple "/" at the beginning of the query string.
Whenever I enter
/192.168.178.1
into the Omnibox and hit enter it works for all services.
If some other people could verify this - I'd be really happy to get some feedback on this approach.
I have this problem often myself. First, go to just localhost, chrome should understand that, then, when you type in localhost/my/url/here, the context will allow chrome to understand to treat it as a url.
I uploaded an image earlier today and it works fine so long as i do not type www into the URL in front... We have had this problem multiple times and I have no idea why this keeps happening or what I can do to help the problem...
I have tried to access from multiple browsers and computers to see if it's a caching issue but alas, it does not seem to work...
I have used both google AND the stack overflow search functions in an attempt to find someone else with the same problem. Maybe I'm not very good at googling, but I wasn't able to find someone else. I did find qiestions that asked between the differences between using www and not using it, but not a single of them had files that could be located on one of them while not on the other.
Which website?
A webserver can respond to
domain.com
or
www.domain.com
Some webserver respond to both of them (depending on the configuration), but there is no guarantee.
The keyword is Webserver Domain Binding or Virtual Host here.
You should open DNS configuration page, in CNAME Record section, add more this record:
Whereby, your images will existing on both http://www.example.com and http://example.com
We have 2 different websites. One is xy.com another is xyz.com. The domain xyz.com is redirected to a folder on xy.com\one
This works fine. Now we want a particular link to be opened (for example, www.xyz.com\abc.html). I am placing this file in xy.com\one\abc.html. But when I enter this url, it takes me to home page, instead of abc.html. Though I can open abc.html, by entering www.xy.com\one\abc.html.
I need to open this file, from link, www.xyz.com\abc.html. How to accomplish this??
Regards,
Rahul Jain
I think the problem is your slashes are reversed. Did you keep your url's near a strong magnet?
If you are using apache you might want to have a look at mod_rewrite. There are similar methods available for other servers.
Would be good to know which environment you are using (web server and server side language) and if you are applying the re-direct rules in a programmatic way or via server configuration.
To give a serious reply, there could be several things wrong in the redirect.
You have to setup a redirect from the old domain to the new, by using a .htaccess on the old domain, changing the DNS records for the domain, or probably some other alternatives. Which of these have you used?
In case of the second option the receiving server (xy.com) has to accept the incoming domain (xyz.com). When I set my DNS records for a domain to go to a certain server, I have to actually setup the server to accept that domain, usually by "parking" it in Cpanel. Some hosts charge per parked domain, which is why they don't accept the incoming traffic automatically.
Depending on the method used, the receiving server has to be told what to do with the request.
So most importantly: HOW did you set up the redirect? Was it a DNS record? Was it a htaccess on the side of xy.com? Any other methods? (sorry, this isn't really an answer either but it was too long for the comments)
What is the difference between the following URLs?
http://www.forums.example.com and
http://forums.example.com ?
Actually I've created a new subdomain in my website and it's working fine when I try to access without www (i.e http://forums.example.com) But when I try to give URL like http://www.forums.example.com it is showing "Page not found".
Why is this and how can I fix the issue?
If I am not mistaken, www. is also considerd a Subdomain, hence when you setup hosting on a provider (i.e Slicehost) they tell you to put www in the subdomain list (again if I am not mistaken). If you really want www.fourms.duckyetc you can set up a script to do some matching, i.e
if url contains www.fourms.ducketc then go to here else go somewhereelse
You have to create a cname for www.forums.duckyvideos.com and also configure your webserver to respond to that cname. There is nothing automatic about www prefixes on the web. It's just a convention that websites are accessible with or without the www. Everyone hosting a website has to explicitly set up a second cname for the www prefixed version of every site they put up.