Home > OS >  The host machine cannot be accessed through the host - only network in Virtualbox Ubuntu Server Web
The host machine cannot be accessed through the host - only network in Virtualbox Ubuntu Server Web

Time:10-04

Hi, dear Daniel:

I in Virtualbox Win10 system installed a Ubuntu Server, it contained the Bitnami Redmine, version for V4.0. X, also brought the SVN service
I give Ubuntu hung up the two pieces of card, a set of bridge host network adapter, a set of host - only, assigned to address are:
The host - only: 192.168.56.101
Bridge card: 192.168.1.93

The question now is, I Cannot be accessed through the host - only the network virtual machine web service, prompt can't open web page, always Reached, such as

But:
1. The host can through the host - only the network Ping virtual machine
2. The host can be used by the host - only network virtual machine SVN service
3. The host can pass the bridge card (IP 192.168.1.93) access web services,

This is how to return a responsibility? Where there is something wrong with the set?

Novice, annexes is

CodePudding user response:

Their top once, no one CARES to answer this question?

CodePudding user response:

Look at your web service is to monitor all of the IP, then check off the firewall

CodePudding user response:

refer to the second floor zhouchao6 response:
look at your web service is to monitor all of the IP, and then look at the firewall off no


HTTPD. This configuration should be monitored in the conf all IP?

#
 
# Listen: Allows you to bind the Apache to specific IP addresses and/or
Home # ports, the default. See also the & lt; VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as to the to
# hasting Apache from glomming onto all bound IP addresses.
#
# Listen 12.34.56.78:80
Listen to 80



Firewall should not open, and if the firewall that should be all IP cannot access, right?

CodePudding user response:

Is the fear you have for card or IP firewall strategy, didn't open it ruled out
You use netstat NLTP - look at the state of the port 80
I just thought of the two possible,,,

CodePudding user response:



The
reference 4 floor zhouchao6 reply:
is a fear you have for card or IP firewall strategy, not open it ruled out
You use netstat NLTP - look at the state of the port 80
I just thought of the two possible,,,


The result is such, can show what problem?

Swadmin @ software - server: ~ $sudo netstat NLTP
/sudo password for swadmin:
An Active Internet connections (only the servers)
The Send Proto Recv - Q - Q Local Address Foreign Address State PID/Program nam e
TCP 0 0 127.0.0.1:0.0.0.0:41839 * 2378/LISTEN Passenger Ruby
TCP 0 0 0.0.0.0:0.0.0.0:80 * 2255/HTTPD LISTEN. Bin
TCP 0 0 127.0.0.53:53 0.0.0.0: * LISTEN/systemd - 4887 re solr
TCP 0 0 0.0.0.0:22 0.0.0.0: * 1176/SSHD LISTEN
TCP 0 0 127.0.0.1:0.0.0.0:6010 * 5150/SSHD LISTEN: swad min @
TCP 0 0 127.0.0.1:0.0.0.0:6011 * 5258/SSHD LISTEN: swad min @
TCP 0 0 0.0.0.0:3690 0.0.0.0:2304/. * LISTEN svnserve. Bin
TCP 0 0 127.0.0.1:3306 0.0.0.0: * LISTEN 2194/mysqld. Bin
22 tcp6 0 0: : : : : : * 1176/SSHD LISTEN
Tcp6 0:0:1:6 010: : : * 5150/SSHD LISTEN: swad min @
Tcp6 0:0:1:6 011: : : * 5258/SSHD LISTEN: swad min @
Tcp6 0 0: : : 443: : : * LISTEN 2255/HTTPD. Bin


CodePudding user response:

80 port is not the problem, it is 0.0.0.0, to monitor all IP
Then, I really don't know what reason be

CodePudding user response:





refer to 6th floor zhouchao6 response:
80 port is not the problem, is 0.0.0.0, listening all IP
Then, I really don't know is what reason


Anyway, thank you for your enthusiastic!!!!!
  • Related