Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
Unable to get to antman (Nano)
Hi guys,
I have searched across the whole forum and while I see similar issues to the one I am having, I failed to find a solution. I opened a ticket with support and the speed of response is like one message a day.
The problem: I am able to connect to the Nano via SSH but I am unable to connect to the antman web portal. I am using the ip address. I already have updated the antman to whatever is their latest release but still nothing. All I get is
This site can’t be reached
192.168.1.112 took too long to respond.
If don't get this to work, this whole project will end up being just a very expensive Raspberry PI.
Much appreciated any help.
I have tried that with the same result:
This site can’t be reached
192.168.1.112 took too long to respond.
I've noticed the Nano takes an incredibly long time before antMan is ready. I've waited over 20 minutes before it would come up using both the xxx.xxx.xxx.xxx:3000 and hostname.antsle.us in the browser.
BTW, I'm assuming you are using the ethernet connection and not wifi. Antman does not work via WiFi at all.
Off course I am using the Ethernet connection and it the nano has been up for more than 20 hours.
Below are the ports this thing is listening on. Not sure if there is anything missing. Honestly, I didn't sign up to be a beta tester of this Nano thing. I just wanted something simple to play with VMs and Docker images but this is obviously something also.
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 669/rpcbind
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 6654/nginx: master
tcp 0 0 10.1.1.7:53 0.0.0.0:* LISTEN 1998/dnsmasq
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 1839/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1529/sshd
tcp 0 0 0.0.0.0:6880 0.0.0.0:* LISTEN 6654/nginx: master
tcp6 0 0 :::111 :::* LISTEN 669/rpcbind
tcp6 0 0 :::80 :::* LISTEN 6654/nginx: master
tcp6 0 0 :::22 :::* LISTEN 1529/sshd
tcp6 0 0 :::3000 :::* LISTEN 6550/java
tcp6 0 0 127.0.0.1:43999 :::* LISTEN 6103/java
udp 0 0 0.0.0.0:50367 0.0.0.0:* 672/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 672/avahi-daemon: r
udp 0 0 10.1.1.7:53 0.0.0.0:* 1998/dnsmasq
udp 0 0 192.168.122.1:53 0.0.0.0:* 1839/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 1998/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 1839/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:* 1324/dhclient
udp 0 0 0.0.0.0:111 0.0.0.0:* 669/rpcbind
udp 0 0 127.0.0.1:323 0.0.0.0:* 687/chronyd
udp 0 0 0.0.0.0:842 0.0.0.0:* 669/rpcbind
udp6 0 0 :::111 :::* 669/rpcbind
udp6 0 0 ::1:323 :::* 687/chronyd
udp6 0 0 :::842 :::* 669/rpcbind
Quote from ivanrdgz on May 30, 2020, 11:48 amOff course I am using the Ethernet connection and it the nano has been up for more than 20 hours.
Understood.
from your ssh session try: service antman restart
Also go to the downloads section of anthill and grab the .iso for the nano... perhaps you just need to remake the micro-sd card with a fresh image.
Hope that helps.
Marc,
I already tried all that. Still the same result.
Fresh image, service antman restart, reboot, prayers and even some hula hooping dancing.
Thank you everyone anyways for the help. I think I will be returning this Nano experiment back to their lab.
Regards,
For one last try, what if you restart nginx, then restart antman ?
service nginx restart
service antman restart
Wouldn't you think that restarting (powering off and on) the device around 20 times already should have helped? For the sake of the experiment, I just tried it and same result.
Regards,