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.
myantsle.local has never worked... 🙁 (Resolved)
So I unbox and follow the instructions exactly. Yet, after 1 hr I still can load http://myantsle.local I can, however, ssh [email protected] and go about performing an upgrade via upgrade-antman 3.0.0d which managed to complete. I managed to get it registered in anthill which was able to reconfigure it including changing the password so clearly it can communicate to the main hive. Yet, I still get load http://myantsle.local which is extremely frustrating.
any ideas ?
Hi @rmcilmoyle!
Could you please ssh in to your antsle and see if antMan is running? You can do that by running `service antman status`
If you can ssh in using myantsle.local, then it obviously has the right IP address - so could you also see if http://myantsle.local:3000 lets you access antMan?
Best, Marc
In the end, I managed to dig my way through getting it all working. It was a bit of a journey. These are the steps I followed;
- managed to create my anthill account
- via SSH and command-line upgrade to the current release 3.0.0d, which ultimately prompted me for the certificate.
even with Chrome I was not able to get AntMan UI up until I managed the upgrade - discovered that only a Chrome browser (on OSX Mojave) was able to interact with Antman reliability.
At this point my nano is up and running; however, it's still saying that I don't have Business Plan.
One thing I discovered with my Nano is you have to be patient with Antman when the Nano reboots or you do an upgrade.
Antman when it is fully up provides port 3000/tcp which Nginx proxies external calls for port 80/tcp into. Typically I just watch for this line in /var/log/messages:
Mar 5 19:23:48 myantsle antmand: antHill init!
When you see that, you know that antmand has finally plumbed up port 3000/tcp and the web GUI should now work.
That said, on my Nano, it typically takes between 8-10 *minutes* before the above happens. Hence, my comment about being patient.