So I'm setting up a vm on virtualbox with Centos. I was able to configure everything fine and with a bridge connection, I have access to the internet and the VM has an IP within the network. From the host I can ssh into the vm without a problem. Now here's the issue, for some reason if I load up the gui from the browser I can access https sites but not http sites.
I noticed this after I tried to install some applications but all mirrors were timing out. Anyone have any clue what this could be?
Related
I am working with Minikube on VM (VirtualBox - Linux Ubuntu). I need to access the ONAP Portal App service's GUI through the internet browser, which I can't.
I have deployed ONAP Portal App on Minikube and now I want to access its GUI through the internet browser. There was no external IP when I looked at "kubectl get services". As I found I used the Minikube tunnel. Now, I have the external IP by the portal-app service (which is by the way same as the cluster IP), but I can't get to its GUI - the website is unreachable/unable to connect. Then I tried "minikube service portal-app --url", which showed me different IP with the correct port, but in the browser I got to the apache tomcat and not to the portal-app. What am I missing?
Thanks for any advice.
On my computer I have deployed my web site on IIS. If I access this website locally with :8080 works perfect, but when I try to access this site from another machine or my Android phone I get 'The site can't be reached. my_ip_address took too long to respond ERR_CONNECTION_TIMED_OUT –' this error.
I have tried solutions from this question, but nothing worked for me. Need some help!
There are few factors which can affect the accessibility of the site hosted on your local computer:
Is the client machine (including your phone) in the same network as the Server (In this case your site)
Is the firewall configured to allow connections on port 8080
Have you tried accessing the server using the IP Address. For e.g. http://192.168.0.1:port
Steps to isolate
Ping the server Ip from the client machine and see if it is able to connect to it.
ping 192.168.0.1
If the above fails, then I would assume that you are not on the same network. If it succeeds then check if the port is open.
You can also use nmap to see whether the ports are open or not
nmap -p 8080 kaushal.com
If the above fails, then open the port in your Firewall configuration and then try again.
Try this and share the results.
I have a website hosted in IIS in my local PC.
I can access to my IIS from other computers in the network by typing in http://my_lan_IP. However, when I try to get access to a specific port (http://my_lan_IP:8888) in my local PC, it says the "The site can't be reached."
I disabled all my firewalls and even tried allowing the specific port through Windows Firewall, but it didn't work. Viewing my IIS hosted site on other machines on my network
Thanks so much for your help :)
FYI: I am using Windows 10. My goal is to connect to the locally hosted ASP.NET website from other machines on the network.
Your web server needs to be configured to serve HTTP on port 8888 "for that particular website", in order for a client to connect to that port.
By default, your website is served on port 80, which is omitted from normal addresses. All http web addresses, if not specifying a port, is actually running on port 80, or 8080.
Your windows firewall will not effect local connections you make to your own pc. Get it working on your own machine, and then worry about firewalls that block connections from other machines on the network.
I was able to solve the issue by configuring a host header for a website. Thank you all for your help :)
https://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
I've got an IBM-Server inside my Network (IP= 192.168.178.10, running on ESXI 5.5)<
Inside this host, I've got 3 VMs running (IPs = 192.168.178.97 - 192.168.178.99, Each Windows Server 2012)
Inside these VMs I've got XAMPP Apache Servers running.
My question is:
How do I make the XAMPP pages visible to the home network? Because every time I open the IPs inside my browser of my laptop (IP = 192.168.178.26), Chrome says that the Server is unavailable.
Strangely - If I type exactly same IP inside the browser of one VM, I can open the pages...
I can also access my Laptop XAMPP Server from inside the VM.
OK - I found the solution myself:
Apache seems to have opened the ports in the firewall, but somehow windows partly blocked the network communication - don't ask me how exactly, but I solved the problem by resetting the firewall, windows network settings and apache/xampp
I have a Windows Vista laptop running IIS7 for its localhost. On this machine, I can successfully navigate to:
"http://localhost"
"http://127.0.0.1"
"http://mycpuname"
However, I cannot access this localhost website from another computer on the same network. Ideally I would be able to visit "http://mycpuname" (so that I can hard-code a connection), but at this point I might settle for the IP address of the machine (http://192.000.000.xyz)
I've seen similar questions asked here and elsewhere on the internet... but none of the posts seems to fix the issue for me.
Things I've tried:
- adding exceptions to Windows Firewall to allow TCP ports 80 and 8080
- disabling Windows Firewall entirely
- running the "netsh" commands in this post
Additionally, I am looking at the IP address on the Windows laptop by running "ipconfig" from the command prompt. Oddly enough, trying to access "http://192.000.000.xyz" from the Windows laptop doesn't seem to work...
I have also tried restarting IIS and restarting my machine.
Help?
Go to windows firewall with advanced security, inbound rules and check and see if world wide web services is enabled. I had this same issue, and this fixed it for me.
are you binding to 127.0.0.1? run below command
netstat -an |findstr :80 |findstr LISTEN
if it shows 127.0.0.1, you need change IIS listen to 0.0.0.0
Try netstat -na - it will show you what IP addresses your web server is listening on.
If it's only listening on 127.0.0.1, the loopback, you will have to re-configure the web server to listen on all addresses/interfaces (usually either *.*.*.*, or 0.0.0.0 in some config file, or just some drop-down in some windows dialog somewhere).
If, on the other hand, netstat tells you the web server is listening on *.*.*.* or 0.0.0.0, i.e. all interfaces, then you have to figure out what's blocking the traffic - it's either the local firewall, or something on the path between the two computers.
If you want to access your website from any other computer on your local network then you need to simply type your network IP and port. If you want to access it from internet then you need to configure your IP.