Common Networking Troubleshooting

Common Issues and Fixes

No IP Address Assigned (Networking Failed to Start)

Symptoms

Cannot access the web sites
ElasticSearch failed to start due to network issue  

Possible Problem and Solution

Interface name was changed by virtualization technology on import of the OVF. This is very common when using VirtualBox

Verify the network interface is set to to NAT or Bridged in the VM technology.

Determine the name of the new interface name assigned by the VM technology by running the following command:

ifconfig -a # capture the name of the network interface to use  

Here is an example with the new interface name circled in red (in this case it's enp0s17)

Perform the following commands and ensure to take note of the interface name assigned by the VM technology to use in these commands. This will replace the existing interface name that came with the OVF to the new name. If there are any issues it's possible to manually update /etc/network/interfaces and replace the existing interface name (usually ens33) with the new interface name.

new_int="insert the correct interface here" # must keep the double quotes
org_int=$(tail -3 /etc/network/interfaces /etc/network/interfaces |grep -v The |awk '{print $2}|sort|uniq)
sudo sed -i "s/$org_int/$new_int/g" /etc/network/interfaces
sudo service networking restart
ifconfig -a # confirm there is now an IP address on the new interface (in this case it's `enp0s17`)

Here is an example of the enp0s17 interface with an IP address assigned

You should now be able to open a local browser and connect to SSH, TimeSketch, Kibana, and Cerebro via that address. If anything is not responding try rebooting the primary services:
sudo systemctl restart elasticsearch timesketch kibana cerebro