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.
I can not access to the antlet##.local
Quote from fdvalero on March 6, 2018, 8:22 amHello,
After the last update,I'm trying to access to any of my antletXX.local
without success.
I tried clear the cache on the browser, restarting the box, also my laptop,
I tried from another pc in the network, and the same result.
If I log in to any of the antlets, and then try to load the web server for any of the antlets, it loads very well, but not from my laptop as I always did before the last update.
This is from one of the antlets:
[srv_ansible@antlet70 ~]$ hostname ; ip a | grep "inet "
antlet70
inet 127.0.0.1/8 scope host lo
inet 10.1.1.70/24 brd 10.1.1.255 scope global dynamic eth0
[srv_ansible@antlet70 ~]$ curl http://antlet61
Hello from antlet61
[srv_ansible@antlet70 ~]$ curl http://antlet62
Hello from antlet62
[srv_ansible@antlet70 ~]$ curl http://antlet71
antlet71 , 10.1.1.71
[srv_ansible@antlet70 ~]$
But from the browser I'm getting this:
This site can’t be reached
antlet61.local’s server IP address could not be found.
Try:
Checking the connection
Checking the proxy, firewall, and DNS configuration
ERR_NAME_NOT_RESOLVED
Regards
Fidel Valero
Hello,
After the last update,I'm trying to access to any of my antletXX.local
without success.
I tried clear the cache on the browser, restarting the box, also my laptop,
I tried from another pc in the network, and the same result.
If I log in to any of the antlets, and then try to load the web server for any of the antlets, it loads very well, but not from my laptop as I always did before the last update.
This is from one of the antlets:
[srv_ansible@antlet70 ~]$ hostname ; ip a | grep "inet "
antlet70
inet 127.0.0.1/8 scope host lo
inet 10.1.1.70/24 brd 10.1.1.255 scope global dynamic eth0
[srv_ansible@antlet70 ~]$ curl http://antlet61
Hello from antlet61
[srv_ansible@antlet70 ~]$ curl http://antlet62
Hello from antlet62
[srv_ansible@antlet70 ~]$ curl http://antlet71
antlet71 , 10.1.1.71
[srv_ansible@antlet70 ~]$
But from the browser I'm getting this:
This site can’t be reached
antlet61.local’s server IP address could not be found.
Try:
Checking the connection
Checking the proxy, firewall, and DNS configuration
ERR_NAME_NOT_RESOLVED
Regards
Fidel Valero
Quote from Johannes Dietzel on March 6, 2018, 4:05 pmThanks for reporting. We identified that there was a misspelling in the names being advertised. We will check our script.
Thanks for reporting. We identified that there was a misspelling in the names being advertised. We will check our script.
Quote from clajo04 on March 7, 2018, 5:21 amI'm having the same problem - can you let us know the misspelling so that we can continue to access the antlets while you work on a fix to the script?
I'm having the same problem - can you let us know the misspelling so that we can continue to access the antlets while you work on a fix to the script?
Quote from Mario on March 7, 2018, 9:32 amIf your antsle still has the original name 'myantsle' when you run the 0.9.1a update, the script was changing the 'antletX.local' names to 'myantsleX.local'
To fix this we can edit the antletsld script.
nano /usr/local/bin/antletsld
Near the bottom there are two 'for' loops, each with a 'name = ...' assignment. We want to change these back to 'antlet-' and 'antlet':
for each in xrange(10, 255):
name = "antlet-" + str(each)
publish_cname(name)
for each in xrange(10, 255):
name = "antlet" + str(each)
publish_cname(name)
If your antsle still has the original name 'myantsle' when you run the 0.9.1a update, the script was changing the 'antletX.local' names to 'myantsleX.local'
To fix this we can edit the antletsld script.
nano /usr/local/bin/antletsld
Near the bottom there are two 'for' loops, each with a 'name = ...' assignment. We want to change these back to 'antlet-' and 'antlet':
for each in xrange(10, 255):
name = "antlet-" + str(each)
publish_cname(name)
for each in xrange(10, 255):
name = "antlet" + str(each)
publish_cname(name)
Quote from Mario on March 9, 2018, 8:12 amAfter making the above edits to the 'antletsld file, restart the avahi-daemon.
From the command line:
service avahi-daemon restart
Or in antMan > Settings (Gear menu item) > System services
After making the above edits to the 'antletsld file, restart the avahi-daemon.
From the command line:
service avahi-daemon restart
Or in antMan > Settings (Gear menu item) > System services
Quote from akak01000101 on March 13, 2018, 9:07 amWhen I made the changes and go to antletXX.local, it redirects to [mydomain].antsle.us page.
When I made the changes and go to antletXX.local, it redirects to [mydomain].antsle.us page.
Quote from akak01000101 on March 13, 2018, 9:30 amAfter further testing... It appears to happen with Firefox, Opera and Chrome. Clearing cache or restarting browser has no affect. Any thoughts?
After further testing... It appears to happen with Firefox, Opera and Chrome. Clearing cache or restarting browser has no affect. Any thoughts?
Quote from brianosaur on March 13, 2018, 9:41 amI also got things to show up in Chrome on Windows 10. Internet Explorer (Edge) and Firefox are both showing timeouts (some on Firefox redirect me to the anthill site). I added the IPs to the host file as well. No luck.
I also got things to show up in Chrome on Windows 10. Internet Explorer (Edge) and Firefox are both showing timeouts (some on Firefox redirect me to the anthill site). I added the IPs to the host file as well. No luck.
Quote from Mario on March 13, 2018, 10:35 amTry commenting out the IPv6 line in the virtual hosts file for .antsle.us
nano /etc/nginx/virtualhosts/ssl.antsle.us.local.conf
Comment out or delete the line listening on IPv6
server {
listen 80;
#listen [::]:80;Restart nginx
service nginx restart
If it works in an incognito or private browser window but not in a regular browser window, clear the browser cache and try again.
Try commenting out the IPv6 line in the virtual hosts file for .antsle.us
nano /etc/nginx/virtualhosts/ssl.antsle.us.local.conf
Comment out or delete the line listening on IPv6
server {
listen 80;
#listen [::]:80;
Restart nginx
service nginx restart
If it works in an incognito or private browser window but not in a regular browser window, clear the browser cache and try again.
Quote from akak01000101 on March 13, 2018, 3:22 pmSame result no change in either a private browser window or a regular browser window.
Same result no change in either a private browser window or a regular browser window.