It was rather a pain in the buttocks, but both ngrok and D0x-k1t are running dockerized. Ngrok is correctly assigning a temporary domain name and is tunneling correctly. So, 🎉
BUT, D0x-K1t is only listening for connections on localhost, so it is currently unreachable. D0xK1t or rather flask needs to be configured to listen for connections at 0.0.0.0. The flask manual states that this can be done by executing the command, flask --host 0.0.0.0. Unfortunately, in order to do this, the application has to be configured to respond to the flask command, and is required to be named app.py. Regardless, both you and I know that if there is a CLI flag, then there HAS to be an internal variable that can be configured through the API to achieve this. I started rummaging through the API docs, but need to focus on fixing my EMACS configuration for the remainder of the night. Since you wrote the app, you are probably better suited to tackle this. I haven't touched flask.
anoduck
commented
1 year ago
It was rather a pain in the buttocks, but both ngrok and D0x-k1t are running dockerized. Ngrok is correctly assigning a temporary domain name and is tunneling correctly. So, 🎉
BUT, D0x-K1t is only listening for connections on localhost, so it is currently unreachable. D0xK1t or rather flask needs to be configured to listen for connections at
0.0.0.0. The flask manual states that this can be done by executing the command,flask --host 0.0.0.0. Unfortunately, in order to do this, the application has to be configured to respond to the flask command, and is required to be namedapp.py. Regardless, both you and I know that if there is a CLI flag, then there HAS to be an internal variable that can be configured through the API to achieve this. I started rummaging through the API docs, but need to focus on fixing my EMACS configuration for the remainder of the night. Since you wrote the app, you are probably better suited to tackle this. I haven't touched flask.Cheers.