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.
upgrade to edgeLinux 2.0 issue
Quote from Nike on July 6, 2020, 6:54 pmupgrade to edgeLinux 2.0 issue
After the upgrade, my zpool is already using 22% while there are no antlets
Getting the same name that is had with antmanOS is not working.
cant use strategizeit.antsle.us or strategizeit.local in the browser or ssh terminal session
Antman GUI, the console is not working, just a black screen after clicking continue of HTTP, also hide console is not working when clicking on it
upgrade to edgeLinux 2.0 issue
After the upgrade, my zpool is already using 22% while there are no antlets
Getting the same name that is had with antmanOS is not working.
cant use strategizeit.antsle.us or strategizeit.local in the browser or ssh terminal session
Antman GUI, the console is not working, just a black screen after clicking continue of HTTP, also hide console is not working when clicking on it
Uploaded files:
Quote from mardo.delcid on July 7, 2020, 4:50 pmHi @nike,
antMan will use some space to store the default templates.
Regarding the console issue, try restarting the docker service:
service docker restart
Hi @nike,
antMan will use some space to store the default templates.
Regarding the console issue, try restarting the docker service:
service docker restart
Quote from Nike on July 7, 2020, 5:39 pmHi Mardo.ceicid,
i upgraded to antman 3.2.1 after that the zpool showed 0% instead of the 22%
However restarting the docker service is did not resolve the console issue i am still getting black screen
Naik
Hi Mardo.ceicid,
i upgraded to antman 3.2.1 after that the zpool showed 0% instead of the 22%
However restarting the docker service is did not resolve the console issue i am still getting black screen
Naik
Uploaded files:Quote from lancem on July 8, 2020, 6:07 amTry opening the console window, then click the Stop link at the top-right corner of the console window.
The console should close, then go back to console (if it doesn't restart, there will be a Start link at the top-right)
Try opening the console window, then click the Stop link at the top-right corner of the console window.
The console should close, then go back to console (if it doesn't restart, there will be a Start link at the top-right)
Quote from Nike on July 9, 2020, 12:52 pmHi Lancem,
Using the stop and start button on the console did not help, still getting a black screen.
Naik
Hi Lancem,
Using the stop and start button on the console did not help, still getting a black screen.
Naik
Quote from Grasume on July 9, 2020, 2:31 pmCan you get to it via SSH ?
Could be a network / router issue.
Can you get to it via SSH ?
Could be a network / router issue.
Quote from Nike on July 12, 2020, 1:09 amYes via a terminal it works. getting the ecsda creation message.
In the console it is just a black screen.
However i raised a support ticket and it working now.
The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me.
Yes via a terminal it works. getting the ecsda creation message.
In the console it is just a black screen.
However i raised a support ticket and it working now.
The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me.
Quote from anagnorisis on September 24, 2020, 3:45 pmQuote from Nike on July 12, 2020, 1:09 amYes via a terminal it works. getting the ecsda creation message.
In the console it is just a black screen.
However i raised a support ticket and it working now.
The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me.
This worked for me after fighting with it for a while.... strange.
Quote from Nike on July 12, 2020, 1:09 amYes via a terminal it works. getting the ecsda creation message.
In the console it is just a black screen.
However i raised a support ticket and it working now.
The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me.
This worked for me after fighting with it for a while.... strange.
Quote from Kevin Clukey on September 27, 2020, 6:41 amI used the work-around mentioned above:
"The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me."
This worked for me. I wonder if it has to do with the "first time question" that prompts for a "yes/no" response.
Thanks for posting this.
I used the work-around mentioned above:
"The trick is to open antAid session after open the console with will ask the to create the ecdsa message, after that close the antAid session, then the console works fine for me."
This worked for me. I wonder if it has to do with the "first time question" that prompts for a "yes/no" response.
Thanks for posting this.