I have installed Rancher 2 Quickstart via Vagrant and VirtualBox. But I cannot access the http://172.22.101.101/ (Rancher Admin page from my host browser). I can successfully ping the http://172.22.101.101/
I have tried setting firewall rules in Norton security and internet connections settings, but has no effect as the Chrome browser states:
This site can’t be reached
172.22.101.101 refused to connect.
Try:
- Checking the connection
*Checking the proxy and the firewall](chrome-error://chromewebdata/#buttons)
ERR_CONNECTION_REFUSED
Reload
HIDE DETAILS
Check your Internet connection
Check any cables and reboot any routers, modems, or other network devices you may be using.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
If you use a proxy server…
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don’t believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings… > Change proxy settings… > LAN Settings and deselect “Use a proxy server for your LAN”.
Windows 10 Pro has the ipconfig as
Ethernet adapter VirtualBox Host-Only Network #6:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::35cf:ea16:6f44:a621%10
IPv4 Address. . . . . . . . . . . : 172.22.101.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Vagrant ssh has
eth1 Link encap:Ethernet HWaddr 08:00:27:60:3F:DD
inet addr:172.22.101.101 Bcast:172.22.101.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:529 (529.0 B) TX bytes:688 (688.0 B)
ping 172.22.101.101 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.042/0.111/0.159 ms
vagrant up
Config: {“default_password”=>“XXXXX”, “version”=>“latest”, “kubernetes_version”=>“v1.11.2-rancher1-1”, “ROS_version”=>“1.4.0”, “server”=>{“cpus”=>1, “memory”=>1500}, “node”=>{“count”=>1, “cpus”=>1, “memory”=>1500}, “ip”=>{“master”=>“172.22.101.100”, “server”=>“172.22.101.101”, “node”=>“172.22.101.111”}, “linked_clones”=>true, “net”=>{“private_nic_type”=>“82545EM”, “network_type”=>“private_network”}}
Bringing machine ‘server-01’ up with ‘VirtualBox’ provider…
Bringing machine ‘node-01’ up with ‘VirtualBox’ provider…
==> server-01: Checking if box ‘chrisurwin/RancherOS’ is up to date…
==> server-01: A newer version of the box ‘chrisurwin/RancherOS’ is available and already
==> server-01: installed, but your Vagrant machine is running against
==> server-01: version ‘1.2.0’. To update to version ‘1.4.0’,
==> server-01: destroy and recreate your machine.
==> server-01: Clearing any previously set forwarded ports…
==> server-01: Clearing any previously set network interfaces…
==> server-01: Preparing network interfaces based on configuration…
server-01: Adapter 1: nat
server-01: Adapter 2: hostonly
==> server-01: Forwarding ports…
server-01: 22 (guest) => 2222 (host) (adapter 1)
==> server-01: Running ‘pre-boot’ VM customizations…
==> server-01: Booting VM…
==> server-01: Waiting for machine to boot. This may take a few minutes…
server-01: SSH address: 127.0.0.1:2222
server-01: SSH username: rancher
server-01: SSH auth method: private key
server-01: Warning: Connection reset. Retrying…
server-01: Warning: Connection aborted. Retrying…
==> server-01: Machine booted and ready!
[server-01] No installation found.
Updating GuestAdditions skipped.
==> server-01: Setting hostname…
==> server-01: Configuring and enabling network interfaces…
==> server-01: Machine already provisioned. Run vagrant provision or use the --provision
==> server-01: flag to force provisioning. Provisioners marked to run always will still run.
==> node-01: Checking if box ‘chrisurwin/RancherOS’ is up to date…
==> node-01: Clearing any previously set forwarded ports…
==> node-01: Fixed port collision for 22 => 2222. Now on port 2200.
==> node-01: Clearing any previously set network interfaces…
==> node-01: Preparing network interfaces based on configuration…
node-01: Adapter 1: nat
node-01: Adapter 2: hostonly
==> node-01: Forwarding ports…
node-01: 22 (guest) => 2200 (host) (adapter 1)
==> node-01: Running ‘pre-boot’ VM customizations…
==> node-01: Booting VM…
==> node-01: Waiting for machine to boot. This may take a few minutes…
node-01: SSH address: 127.0.0.1:2200
node-01: SSH username: rancher
node-01: SSH auth method: private key
node-01: Warning: Connection reset. Retrying…
node-01: Warning: Connection aborted. Retrying…
node-01: Warning: Connection reset. Retrying…
node-01: Warning: Connection aborted. Retrying…
==> node-01: Machine booted and ready!
[node-01] No installation found.
Updating GuestAdditions skipped.
==> node-01: Setting hostname…
==> node-01: Configuring and enabling network interfaces…
==> node-01: Machine already provisioned. Run vagrant provision or use the --provision
==> node-01: flag to force provisioning. Provisioners marked to run always will still run.