After setting up InstantSSL on anthill, AntMan now fails in the browser.
http://<hostname>.local - shows the login page, but after the login page blank page.
https://<hostname>.local - cannot connect to server
http://<hostname>.antsle.us - shows 502 Bad Gateway (nginx/1.16.0)
https://<hostname>.antsle.us - can't connect to the server
http://<ipaddress> can't connect to server
http://<ipaddress>:3000 hangs
https://<ipaddress>:3000 can't connect
Confirmed with 'dig' that the antsle.us subdomain resolves to the correct local network IP address.
I'm able to ssh into the antsle using the subdomain.
{"version":"2.2.0b","edgeLinux-version":"2.2.0b","anthilld-version":"1.2.7","early-access-promo-due":1535525940000}
Hi @ansontsao,
Please run `antsleOS-logs antman`, and in a separate terminal session run `service antman restart`, if any errors pop out please send them here.
I have the same result. I installed the Instant SSL on my new Nano, and now I get teh 502 Bad Gateway message.
Make sure, after you set up SSL, that you're using an https and not http URL!
I get bitten by that occasionally.
Here are log. still getting bad gateway after installing SSL
2020-04-07 21:40:22,347 [Thread-3] INFO antman.core - #'antman.core/http-server stopped
2020-04-07 21:40:22,348 [Thread-3] INFO cronj.data.timer - The timer is already stopped.
2020-04-07 21:40:22,348 [Thread-3] INFO antman.core - #'antman.handler/init-app stopped
2020-04-07 21:40:39,156 [main] INFO antman.env -
-=[antman started successfully]=-
2020-04-07 21:40:54,167 [main] INFO luminus.http-server - starting HTTP server on port 3000
2020-04-07 21:40:55,085 [main] INFO antman.core - #'antman.config/env started
2020-04-07 21:40:55,329 [main] INFO antman.core - #'antman.handler/init-app started
2020-04-07 21:40:55,531 [main] INFO antman.core - #'antman.core/http-server started
2020-04-07 21:40:55,728 [main] INFO antman.core - #'antman.core/repl-server started
2020-04-07 21:45:14,426 [Thread-3] INFO luminus.http-server - HTTP server stopped
2020-04-07 21:45:14,428 [Thread-3] INFO antman.env -
-=[antman has shut down successfully]=-
2020-04-07 21:45:14,430 [Thread-3] INFO antman.core - #'antman.core/repl-server stopped
2020-04-07 21:45:14,431 [Thread-3] INFO cronj.data.timer - The timer is already stopped.
2020-04-07 21:45:14,431 [Thread-3] INFO antman.core - #'antman.core/http-server stopped
2020-04-07 21:45:14,432 [Thread-3] INFO cronj.data.timer - The timer is already stopped.
2020-04-07 21:45:14,432 [Thread-3] INFO antman.core - #'antman.handler/init-app stopped
2020-04-07 21:45:30,769 [main] INFO antman.env -
-=[antman started successfully]=-
2020-04-07 21:45:45,692 [main] INFO luminus.http-server - starting HTTP server on port 3000
2020-04-07 21:45:46,499 [main] INFO antman.core - #'antman.config/env started
2020-04-07 21:45:46,757 [main] INFO antman.core - #'antman.handler/init-app started
2020-04-07 21:45:46,969 [main] INFO antman.core - #'antman.core/http-server started
2020-04-07 21:45:47,169 [main] INFO antman.core - #'antman.core/repl-server started
Was there a solution to this? I think I might be running up against a similar issue.
Hi @wolf
I haven't seen this issue in a while.
What I've seen more often is the SSL certificate expired after 90 days of not communicating with antHill. The certificate for antsle.us will auto expire after there is no communication with antHill.
You can use commands below to restart anthilld service and check its status:
service anthilld restart
service anthilld status
Can you let us know if your antsle.us address resolves to the correct local ip on your network?
Hi @daniel-luck,
Thank you for the help. Much appreciated!
Hypothetically speaking, the issue can be reliably duplicated if you leave a device logged in to Antman, forget about that, and try to access Antman from another device.
Hi @wolf
Thanks for the info. Although I haven't experienced this issue myself, it's good to know.
