When I access the web server (https //: xxx.com) from different devices - cellphone, tablet and pc I get the error ERR_CONNECTION_TIMED_OUT, all the devices are on the same ip address. (when each device has a different ip address everything works ok).
Only the last device can access the web with the other error message ERR_CONNECTION_TIMED_OUT
It is a vps server that has a wmh panel.
this creates a problem for me, when multiple computers from the office need to access an application located on the server, only one can work.
This seems to be a problem with the apache configuration.
Try this IN WHM:
Edit "Global configuration" in Home >> Service Configuration >> Apache Configuration >> Global configuration
Set this config:
Start Servers: 100
Minimum Spare Server: 100
Server limit: 600
Max Request Workers: 1000
Save and click on the button "Rebuild configuration and Restar apache"
Related
i get this error for installation script that worked perfect on EC2 vm but now seems that i can't reach the site , should i add some inbound rule or something to enable apache2 server ? the error in the chrome is
This site can’t be reached *.*.*.*.com’s server IP address could not be found.
Try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Network Security Group
Azure VMs do not have any ports open firewall ports by default unless you open them when you provision your VM. When you created your Azure VM in the Azure Portal, you likely created a Network Security Group for the VM. If you didn't specify any ports to open during the VM's creation, you'll need to open up the VM's firewall.
To Open Ports
To open up the ports on the firewall, head out to the Azure Portal (where you set up the VM). Find the VM in the list of resources. It should take you to a page for your VM where the name, status, location, size, IP address, etc will be displayed. On the left side, you'll have a vertical menu > Select Networking. From there, you'll be able to see currently active firewall rules for the VM. Since you're likely missing HTTP (80) and HTTPS, select add inbound port rule. From the dropdown for service, select HTTP and assign a name/priority. Perform the same options, except this time selecting HTTPS (443). Press save and test. You should be able to access Apache running on the VM.
Additional Troubleshooting
The script you used may have inadvertently set up the VM's iptables. You can view Linux's firewall with sudo iptables -L to verify that no firewall rules have been enabled. Since Azure handles the firewall, you shouldn't need any iptables rules, but they could always be added for additional security.
This answer assumes that you do not have Azure's Load Balancing servers installed in front of the VM.
I uploaded two websites on a single IIS local server. One that hosts a WFC service other that consumes it
I know that using host header to distinguish them in not an option without a DNS server, so I gave the first one an all assigned IP ad the second one 172.20.1.44, whenever I try to browse to it locally it gives me the connection timed out
how could I browse to the second site on my local machine to test it
Put them on different ports. Put one site on * 80 and the other on * 8080. You can modify the port in the binding screen of IIS.
Yesterday I created an Azure Virtual Machine using the simple Win2008r2 + SQL2008r2 image.
I have deployed a website to the VM via an RDP session.
I am able to browse the website locally (via RDP) using
"http://localhost"
I understand that I need to add an Azure endpoint for port 80 to enable me to browse to the site from an external machine.
I have configured the Windows Firewall on the Azure VM to allow traffic on Port 80 inbound and outbound.
Could anyone please advise what I've missed or what I can do to troubleshoot?
---Update-----
I have learned a little more this morning. The website that I'm trying to host on the VM is an installation of Interwoven Teamsite v7.3.x. When I looked in IIS I could see that the "Default Web Site" was stopped. Another website called "TeamSiteSitePubPreview" had been created but was only bound to port 81.
So, what was presenting the website I could see when I browsed to
http://localhost locally?
I ran netstat -ano and this showed me that PID 1604 what listening on port 80. I then ran Process Explorer which told me that PID 1604 was allocated to "Appache HTTP Server".
I know nothing about About Appache, can anyone tell me if there's some Apache config that will be preventing connections from outside of the local server?
For reference, I just tested this sequence and it gives you a website accessible over the Internet:
Create a new Windows Azure virtual machine with the Windows Server 2008 R2 SP1 image.
Add an endpoint on public port 80, private port 80.
While the endpoint is being created, start setting the server up.
Remote Desktop in.
Add the Web Server (IIS) role with default settings.
Test the connection. You should get a HTTP 200 OK status.
If you want to troubleshoot your server, start checking for errors in the event log. Check also the website bindings in IIS (Port 80, IP Address *).
Also consider the connection issue might be on the client (your) side. For instance, DNS caching. Try connecting from another machine with direct Internet connection (such as another cloud server) or from a service such as isup.me.
Additionally, if all you want is to host websites in IIS, the Web Sites service has a more streamlined experience.
You will need to create an endpoint on port 80 thru Windows Azure Management portal as well. This endpoint opens a port in the Windows Azure Load-balancer.
Navigate to your VM within the portal and create a new Endpoint under the Endpoints screen of VM configuration within Azure management portal.
I am adding a new site on a server running other sites, some 'All Unassigned' (those that do not need an SSL) and the is the 4th site with a unique IP (these require an SSL). All other sites, including their SSLs (if applicable) are working.
When I ping the LAN IP from within the network, I get 'request timed out'. Pings to the other unique IPs get a response.
I've tried:
other unique LAN IPs
created a new website in IIS6
created a 'test' folder and pointed IIS there
Event Viewer logs for System or Application show no error messages.
I restarted IIS after each variation.
To my knowledge, pinging from within the network does not go thru my firewall, so I have not fooled with it.
an ASP.NET version issue would ping but throw a browser error, so I have not fooled with it.
Any thoughts on how to debug this issue?
Any suggestions welcome, and Thanks in advance.
Have you added the IP address to the network configuration on the Windows machine?
Ping doesn't have anything to do with your web server configuration or IIS.
To debug:
Make sure under Control Panel -> Network - > under TCP/IP Configuration that your server has the required IPs entered and that your subnet mask entries are correct.
Ping from the command line, so start - > run -> cmd
then at the prompt ping -ip address-
Make sure that your windows firewall is allowing ICMP packets in and out. If your network is protected from the internet by a separate firewall, you can turn the Windows firewall off to test.
I'm using windows server 2008 & IIS 7.0 to deploy the my vb.net 3.5 application.
I'm successfully able to run the URL on my server.
Same URL having IP address & port number configured is not working on client system.
It is showing IE default error message as "page cannot display"
Thanks
A couple of things to do:
Try it in something other than IE - Or at the very least turn off IE "Friendly http error messages" as they obscure the real problem (Tools -> Internet Options -> Advanced)
Make sure the IIS website is bound to all IP Addresses not just 127.0.0.1 (localhost)
Make sure the windows firewall / other firewalls in use are configured to allow incoming traffic on port 80 through (assuming you're using port 80)
Check the event logs - If it's a coding problem, the error message is usually dumped in there
If the client system is on a different network, make sure that all your firewalls/routers are set up to allow the appropriate traffic through
Some more information which would help us:
Where (in network terms) is the client you mention? same network?
What happen if you use the full URL the client's using from a browser on the server?
When you say it works on your server, is that the VS development server? or the same server the client is using?