Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
Here are some tips on how to resolve any problems that might arise.
Here is a series of videos for trouble shooting anthill activation.
1. Basic connectivity
Are you plugged into the correct ethernet port? The default ethernet port is 'br0' and is the only port enabled when new out of the box.
2. antHill, enter SN# and password
The SN# can be found on the bottom of your Antsle.
3. Verify the root password
4. Check anthilld service and internet connectivity
If you need to roll back to the previous version after running an edgeLinux upgrade, follow these steps:
Once you have the USB ready, connect a monitor, a keyboard and the USB stick; then boot from it.
Once in the sysrec OS, download the rollback shell script and execute. You can use the following commands to do so:
After the script finishes, shutdown your server by executing:
Remove the USB stick, and boot normally. You should be able to access your previous environment before the upgrade.
Is the power LED on?
Please check the power adapter is firmly plugged into Antsle's DC power connector and that the power button has been pressed to turn your Antsle on.
Is there a link light on the ethernet port and switch/router?
Are you connected to the same subnet (same switch or vlan) as the Antsle?
Does your computer resolve the .local domain name to an IP address? Test with a ping which should return the private IP address of the Antsle.
If you get google search results instead of antMan you may need to use 'http://' in the url
antMan is listening on port 3000, try
If you know the IP address of the Antsle, you can open antMan with:
You can find the IP address by connecting a keyboard and monitor to the Antsle and login as the root user. At the command line, run:
The avahi service (mDNS) on the Antsle is what advertises the .local names. It uses IP multicast address 224.0.0.251 and udp port 5353. Any chance you have a firewall blocking on your workstation or your router?
Here are the things to keep in mind regarding the InstantSSL. (antsle.us subdomains)
The InstantSSL domain name resolves to the private IP of the antsle as seen in the antMan dashboard (the IP on br0). If this IP is in a private IP address range, e.g. 10.x.x.x, 172.16.x.x thru 172.31.x.x or 192.168.x.x, then it cannot be reached from the public internet. Only from the local LAN.
Nginx on the edgeLinux OS handles the SSL cert and the connection to antMan. The Nginx service should be running. You can check with the command:
The anthilld service queries the antHill database for the antsle.us domain name and handles installing the SSL cert and adding the nginx conifg file for the domain name. The anthilld service should be running
The antsle must be able to communicate with the public internet?
The nginx config file that is created by anthilld is 'ssl.antsle.us.local.conf' and should exist in /etc/nginx/conf.d/
On MacOS or Linux, you can launch the Terminal app.
Run the 'ssh' command
and enter your root password when prompted.
Install an ssh client on your PC, such as PuTTY or MobaXterm.
Start a new ssh session, enter antsle_name.local as the host, root as the user name and use your root password.
You can leave the port at the default setting (22).
http://antlet10.local does not show the antlet.
Some antlets can take considerable time to start up, especially KVM antlets. So please wait a few minutes and try again.
I cannot SSH into my antlet.
Please make sure you've started the antlet and it is shown as Running in antman. Some antlets can take considerable time to start up, especially KVM antlets. So please wait a few minutes and try again.
If the available templates list is empty and you have not downloaded all of our available templates, you may have an ad-blocker plugin in your browser. Try creating an exception for antMan.
Refreshing the Templates page may cause this issue as well. Just navigate to another page and back again and the Available Templates will be populated again.
The error: Internal error: Did not find USB device bus:X device:Y is displayed when starting an antlet with a USB Pass Through device.
The issue here is the USB device number will increment if the USB is removed and plugged back in. Or the USB has been removed before it was disabled in antMan.
Near the bottom you will find the '<hostdev...' section. Edit the 'device=' number with the new device number. Or remove the entire <hostdev... section if the USB is no longer attached to the antsle.
Save and exit. Now the antlet should start.
Wrong number of args (0) passed to: core/juxtThis error will occur if you delete all the templates from 'Manage templates'Getting error: Server responded with 0 codeIf running antsleOS version below 0.4.0 and antman 0.7.0, there is a 16GB limitation if you use http://myantsle.local URL. Look up your Private IP in antman, say it is 192.168.0.103. Then navigate to http://192.168.0.103:3000 to access antman. With that URL, you should be able to import templates bigger than 16GB.
Error: Requested operation is not valid: network 'bblv' is not active.
The internal network (for the antlets) is a NAT'ed network and must be different than the LAN your antsle is connected to. We suggest using 10.1.1. for base-ip. If the LAN the antsle is connected to is using that same network address then the antlets base IP can be changed in antMan > Settings > Base IP.
The base IP can be set from the command line as well with the following command:
replacing x.x.x. with a unique network address. Note, include the last '.'
To start the 'bblv' network from the antlse's command line, run:
If you get an error referencing 'tun', run the following command:
Reboot. You can check the status of the internal networks with:
Mouse cursor not in sync with the display
If the antlet was running during the last upgrade, then you just need to Stop->Wait->Start the antlet; please note that clicking Reboot will not suffice, as it would just trigger Operating System level reboot and it won't reload any changes done on the domain definition.
There are many issues with IE, not recommended.
You can also try clearing your browser cache.
If the antlet was imported you may need to make a change to the xml definition First ssh to the Antsle and run:
and add:
Before the </devices> tag near the bottom.
Currently versions of Windows Server Essentials will not install on the Antsle.
Ethernet port
Bridge name
Interface name
Speed
Port 0
br0
enp0s20f0
10M/100M/1G
Port 1
br1
enp0s20f1
10M/100M/1G
Port 2
br2
enp0s20f2
10M/100M/1G
Port 3
br3
enp0s20f3
10M/100M/1G
Ethernet port
Bridge name
Interface name
Speed
Port 0
br0
eno1
10M/100M/1G
Port 1
br1
eno2
10M/100M/1G
Port 2
br2
eno3
1G/10G
Port 3
br3
eno4
1G/10G
Ethernet port
Bridge name
Interface name
Speed
Port 0
br0
eno3
1G/10G
Port 1
br1
eno4
1G/10G
Modifying the local 'hosts' file can be useful for testing nginx domain name forwarding or if your machine is not working well with mDNS (resolving myantsle.local).The 'hosts' file on your local machine works like a local DNS. Your local machine will first check the local 'hosts' file to resolve a URL before making a DNS request. If the URL is found in the local 'hosts' file the IP address configured will be used and no DNS request will be made.
You can manually enter IP address to host name mappings in this file.
The first column contains the IP address of the host. The second column contains the primary host name. The following columns are aliases. Anything following a '#' sign on a line is ignored (a comment).
On Windows, right click the icon to lauch NotePad and choose 'Run as Administrator'. Then open and edit the 'hosts' file which is located in
On Mac open a terminal and run nano with elevated privileges
On Linux open a terminal and use nano or vi with elevated privileges
You'll need to create a bootable USB stick with the following image:
Is your ethernet cable plugged into the correct ?
Windows does not resolve .local names by default. You may need to install Bonjour print services or iTunes:
You can also try modifying your local
You first need to install something in your antlet, e.g. Apache. See
Try to first, and from there into your antlet.
Please make sure you're using the correct .
I get a 502 Bad Gateway error when connecting to an antlet?If you are trying to connect to an antlet according to the instructions in '' e.g. http://antlet10.local , you must have some web server software installed and running on that antlet.
To resolve this we need to edit the xml for the antlet. In antlet details in the USBs tab get the new device number for your USB. Then from the command line of the antsle: , Open the xml of the antlet for editing with
In case you have any questions or comments, please . Don’t hesitate, we’re friendly.
