Quote from
TheGarnet on July 21, 2020, 1:14 pm
I have a trio of nanos on my local network.
I just tried to log into one of the nanos with its http://nano1.local login. I got the login prompt, entered my password, clicked login, and many minutes later it is still spinning "processing request".
I made this nano the DMZ machine for my router on my comcast internet.
I put a separate machine on a cellular internet connection, went to http://public-ip. got my nano1 login, and was able to login without a huge delay, and even spun up another antlet to play with. Created a login for this forum too.
My nano only has two idling antlets, 1% of cores, and 59% of ram being utilized.
Meanwhile, that first http://nano1.local browser screen is still spinning.
How do I debug this issue?
I just tried hitting stop. And retried the login on this machine, and it worked fine this time. So I now have two different copies of Antman management on display, one from the nano1.local on one machine, one from the public IP DMZ login on another machine.....
I have a trio of nanos on my local network.
I just tried to log into one of the nanos with its http://nano1.local login. I got the login prompt, entered my password, clicked login, and many minutes later it is still spinning "processing request".
I made this nano the DMZ machine for my router on my comcast internet.
I put a separate machine on a cellular internet connection, went to http://public-ip. got my nano1 login, and was able to login without a huge delay, and even spun up another antlet to play with. Created a login for this forum too.
My nano only has two idling antlets, 1% of cores, and 59% of ram being utilized.
Meanwhile, that first http://nano1.local browser screen is still spinning.
How do I debug this issue?
I just tried hitting stop. And retried the login on this machine, and it worked fine this time. So I now have two different copies of Antman management on display, one from the nano1.local on one machine, one from the public IP DMZ login on another machine.....