If you can’t connect to the Snapt interface, it is most likely due to one of two things:
- A firewall on the host.
- The IP is not present on the network cards.
If you are using a Snapt image, you don’t normally need to worry about firewalls as you already have direct access to your Snapt image.
However, if your access is not direct and your Snapt console lies behind a network protected by a firewall, then you should check that you have opened ports 8080 and 8081 for web access.
You may also experience problems with the networking of your Snapt instance.
To check the IP address, run:
You should see your IP address bound to the Ethernet card you chose, on an output similar to this one:
eth1 Link encap:Ethernet HWaddr 00:0C:29:6D:F6:A0 inet6 addr: fe80::20c:29ff:fe6f:f6a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 KB) TX bytes:0 (0.0 KB) Interrupt:32 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:266 errors:0 dropped:0 overruns:0 frame:0 TX packets:266 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 KB) TX bytes:0 (0.0 KB)
If you do not see your IP address or Ethernet card, then your network card may be misconfigured or the IP may already exist on that network.
You can check
/var/log/messages and use the
dmesg command for more information after a reboot.
IP Address Misassignment
Perhaps your Ethernet interface is alright but the IP hasn’t been properly assigned to it yet.
First, check the IP address with the Snapt tool:
If you have no output, try setting the IP address with this other Snapt tool:
You can either use:
- DHCP for automatic assignment,
- Configure an IP address to set the IP manually.
Now try rebooting your Snapt instance and see if the assignment issues have been addressed: