I am facing a strange issue on a single PC, all other PC's I have tried are fine so the problem definitely seems localised to this setup.
Windows 7
Google Chrome Version 48.0.2564.82 m
I have developed a simple website on an Apace web server (Windows Server 2012), and assigned it an internal IP address (1.2.3.4), and internal dns name (MyWebsite.MyDomain).
This website is only available within our company. When I type the URL MyWebsite.MyDomain into any browser I am presented with the correct web page, great. When I type the IP address 1.2.3.4 into any browser I am also presented with the correct web page, great again.
This is the case for every PC I have tried so far, apart from one. Instead I am presented with the following error message;
This web page is not available
ERR_NAME_NOT_RESOLVED
Why would this be?
Things I have tried so far on the local PC;
delete history/cache on local PC
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns
changed to Google public dns (8.8.8.8 / 8.8.4.4)
restart (multiple times)
tried IE and FFOX (same error)
checked hosts file (all looks ok)
The only change I ever made to this individual PC was I installed XAMPP and changed the hosts file (for testing purposes). I have since uninstalled XAMPP and reverted to the original hosts file - could this be the issue? I can't think of any other changes.
I had thought the issue was with my web server setup, but as the web site is accessible from all other PC's it would appear not?
Looks like a re-build may be necessary for this PC, unless somebody can perhaps point me to another suggestion? Any help appreciated.
That machine doesn't happen to have any static ip addressing configured, does it? I'm thinking that perhaps a manual entry for DNS server is conflicting or overriding what DHCP is supposed to be assigning.
Related
I have tried all kinds of things, read all answers, and configured the bananas out of it, but I cannot seem to get the following working:
A windows 2016 server with XAMPP, to host more websites than 1.
What have I done:
I have altered the httpd-vhosts.conf as described all over the web with allowing NameVirtualHost, and setting up virtual host with documentroot, servername etc.
I have pointed a domain with the a-record to this server
installed the latest XAMPP release to date
changed the windows hosts file, as described everywhere (127.0.0.1 domainname.com)
What works:
I can get the domain working on my server's browser. When I enter the specific domainname.com it shows the hello world page I made in the specified folder. The domain resolves and shows the page that is in de directory accordingly
Besides that, the localhost of apache is also working, I have 2 sites working, but only on the browser of the server, on the machine itself.
What does not work:
Only 1 thing. when I want to access the domain from any other machine than the server (from outside so to say), it will not work, but when I ping the domain on my home-pc it resolves to the server.
I am at a loss. Been at this for hours, and beginning to question if it is even possible.
Can anyone tell me what I am doing wrong here, or if it is even possible to have more than 1 website to work on XAMPP and resolve form the outside?
Thank you in advance.
It was windows firewall that stopped all inbound connections. I finally figured it out!
Bit of a strange one - Over the weekend I updated the version of PHP on one of our servers and all seemed to be working fine, however yesterday, we started to receive complaints that the site was down.
After looking in to it, the site works fine when connecting from the internal network, but it times out when trying to connect from an external IP address.
Server admin isn't really my strong suit, so not really sure where to begin. I've checked the httpd.conf files and all looks fine, the apache config test reutrns 'OK' so at a loss as to where to go next.
Server is running Centos, PHP 7.2 and apache 2.4.6.
How can I get the server to respond to external requests?
Andy
You can use this tools (metod) to check where is propably the problem:
I. on serwer, check :
whether is serwer conections to internet - ping, tracerout
whether page is loading (on local) - lynks, links (text web broweser)
whether your dns is working (or dns ISP prowider) - depending on the service used, e.g. BIND (check usage this tool in internet)
whether your firewall is ok configured and good work - depending on the service used e.g. iptables
whether domen settings is ok,
...
II. on computer, check: (in internet, not in local network with your serwer)
whether the website loads in the browser eg firefox after using ip address (your server where the page is located) in www bar
whether host in internet have a contact with your serwer - ping, tracerout
whether the website loads in the browser eg firefox after using ip address (your server where the page is located) in www bar
...
The problem is wery complicadet becouse I dont now what exactly you have an infrastructure and it is settings (network, ISP, etc.) which you on host the page you are writing about. For this reason, it is difficult for you to precisely help.
I have a problem, and maybe I don’t know what do search for, but I haven’t been able to find any threads with a similar problem. So I hope that any of you can point me in the right direction or suggest a solution.
I have a wampserver running on localhost, and I have created a database and a webpage that is using this. When I enter localhost/myproject in the browser the project is displayed. I need to access this site from another device on the same network though, and for that reason I need to use the IP Address of the computer hosting the server (this is 192.168.1.3).
The problem is, that the computer IP is only accessible sometimes. Meaning – if I enter 192.168.1.3/myproject in the browser window, sometimes it will display the webpage as it should while other times it won’t. It either gives me a message of something like “runtime out” or it just keeps trying but never does anything. I can always get access to the router using the IP 192.168.1.1, and here I see the computer 192.168.1.3 even when I can't connect to it.
A while ago I changed the Apache file httpd.conf and added “Allow from 192.168.1.3” under Directory. I did this because I got a message of “access denied” when entering the IP in the browser, and I found a thread posting this solution – which worked. I also created an exception for port 80 in the windows firewall in this process.
I don’t know what to do now though. Any help/suggestions would be very much appreciated, thanks.
Try to increase timeout intervals in your php.ini file
If sometimes it's works, and sometimes - no, problem in timeout
I am using OSX local web server and today I needed to set up a virtual host. After doing so, accessing localhost in a browser hangs. 127.0.0.1 says permission denied. Even after I reverted the changed to the files I made under etc/. What's weird is when I check my web sharing, it says the web server can be accessed via { someone-else's-computer.local/~my comp name }. That someone else is someone who is on the same router as me. When I disconnect my wifi, it says it can be accessed via my computer name. I don't know what's going on.
I figured it out something about what I did while editing it the first time or saving it out using TextMate screwed up the file. I backed up hosts file, duplicated hosts-original, renamed it hosts, and the selected all and pasted the contact back in. So basically the content didn't change, but instead I saved it out of text wrangler this time and magic! It worked. Computers are so annoying sometimes.
I have someone complaining that www.archstl.org (a site I manage) loads fine from his Windows PC, but not on his Mac; and apparently he can't get it anywhere he takes his Mac, either...
I've heard of this happening to one other person, but I can't find an explanation. When they try loading it on their Mac using either Safari or FireFox, they get the default Apache page: "If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page."
I have had him ping www.archstl.org, and it always returns the proper IP address of our server (174.37.22.142), so I don't know what could be going wrong. It seems that our server is sending him the wrong page, plain and simple...?
As it turns out, the dns entry for archstl.org included a self-referring ipv6 address (::), which caused Macs running Apache to go to localhost (ignoring the ipv4 address). Our data center removed the v6 address, and now all is well.