nitrc-ce
nitrc-ce > RE: Getting started with NITRC-CE
Apr 12, 2022 10:04 PM | David Cash
RE: Getting started with NITRC-CE
Hi
Christian-
No worries, I really appreciate you helping out as it's going to be very helpful for some of the teaching activities that we want to do. What was happening was that I was launching a NITRC-CE instance (eu-west-2 as I am based in London) and going to the resulting public IP address per the instructions and not being able to reach the webserver. I was however able to SSH into the machine, and when I did "docker ps", I saw two containers up(guacamole/guac and nitrc/guacamole:1.0), but no httpd container. I then found the error message from one of the docker-compose commands and it was shutting down because the certificate folders were empty. I kept digging and found the maange-ssl.py that is ran as part of the startup and the log it generates in /tmp and this is what it said (this is from a terminated instance):
INFO:root:called with CREATE 14498 18.130.166.210
INFO:root:Connecting to https://t1nn87w4yl.execute-api.us-east-1...
INFO:root:Using key r2kmIRXQzk8X0QunpTgtX5blg4sdXxHS4F8oIhGx
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): t1nn87w4yl.execute-api.us-east-1.amazonaws.com:443
DEBUG:urllib3.connectionpool:https://t1nn87w4yl.execute-api.us-east-1.amazonaws.com:443 "POST /prod/ssl-cert HTTP/1.1" 429 28
DEBUG:root:Create response was "{\"message\":\"Limit Exceeded\"}"
DEBUG:root:done
No worries, I really appreciate you helping out as it's going to be very helpful for some of the teaching activities that we want to do. What was happening was that I was launching a NITRC-CE instance (eu-west-2 as I am based in London) and going to the resulting public IP address per the instructions and not being able to reach the webserver. I was however able to SSH into the machine, and when I did "docker ps", I saw two containers up(guacamole/guac and nitrc/guacamole:1.0), but no httpd container. I then found the error message from one of the docker-compose commands and it was shutting down because the certificate folders were empty. I kept digging and found the maange-ssl.py that is ran as part of the startup and the log it generates in /tmp and this is what it said (this is from a terminated instance):
INFO:root:called with CREATE 14498 18.130.166.210
INFO:root:Connecting to https://t1nn87w4yl.execute-api.us-east-1...
INFO:root:Using key r2kmIRXQzk8X0QunpTgtX5blg4sdXxHS4F8oIhGx
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): t1nn87w4yl.execute-api.us-east-1.amazonaws.com:443
DEBUG:urllib3.connectionpool:https://t1nn87w4yl.execute-api.us-east-1.amazonaws.com:443 "POST /prod/ssl-cert HTTP/1.1" 429 28
DEBUG:root:Create response was "{\"message\":\"Limit Exceeded\"}"
DEBUG:root:done
I was also getting the same error when I
tried to run the command myself after the machine was
launched.
Note: The most recent instance I have
launched as of Tuesday 12 April 23:00 UK time is getting a
certificate.
Originally posted by NITRC
Moderator:
David,
Thanks for reaching out again (and for your patience!) -- if we can see it in action now that it's happening again, we can diagnose it. Can you tell me how you see the "Limit Exceeded" error? The SSL request is done on instance startup, so it shouldn't be exposed. Are you looking in the logs or are you doing the request by hand?
In any case, I'm also going to build a VM for you to download -- this way we'll be working on two fronts to getting you up and running.
Christian
Thanks for reaching out again (and for your patience!) -- if we can see it in action now that it's happening again, we can diagnose it. Can you tell me how you see the "Limit Exceeded" error? The SSL request is done on instance startup, so it shouldn't be exposed. Are you looking in the logs or are you doing the request by hand?
In any case, I'm also going to build a VM for you to download -- this way we'll be working on two fronts to getting you up and running.
Christian
Threaded View
| Title | Author | Date |
|---|---|---|
| David Cash | Mar 31, 2022 | |
| Christian Haselgrove | Apr 1, 2022 | |
| David Cash | Apr 4, 2022 | |
| David Cash | Apr 12, 2022 | |
| NITRC Moderator | Apr 12, 2022 | |
| David Cash | Apr 12, 2022 | |
| Christian Haselgrove | Apr 12, 2022 | |
| David Cash | Apr 12, 2022 | |