# Prodigy doesn't launch or die

**URL:** <https://support.prodi.gy/t/prodigy-doesnt-launch-or-die/4329>\
**Category:** Getting Started\
**Tags:** install, server\
**Created:** [June 14, 2021, 8:05pm UTC](https://support.prodi.gy/t/prodigy-doesnt-launch-or-die/4329 "2021-06-14T20:05:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sudarshan85](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/sudarshan85/32/2199_2.png) [@sudarshan85](https://support.prodi.gy/u/sudarshan85)\
**Post date:** [June 14, 2021, 8:05pm UTC](https://support.prodi.gy/t/prodigy-doesnt-launch-or-die/4329/1 "2021-06-14T20:05:43Z")

</div>

Hi,

I am using Prodigy on a secure environment within an enclave (that has no access to the internet). This is accessed through an RDP connection to a virtual machine. I have installed Prodigy in an anaconda environment. However, when I launch Prodigy two things happen:

1. It launches on its default port 8080, however, when I launch localhost:8080, I am unable to connect to the server despite getting the message "Open the app in your browser and start annotating!"
2. When I try to kill Prodigy using Ctrl-C, it hangs and I have to use Ctrl-Z and kill it manually using kill -9 

It'll be great if I could get some help on this issue.

---

<div class="post-metadata">

**Author:** ![honnibal](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/honnibal/32/35_2.png) [@honnibal](https://support.prodi.gy/u/honnibal)\
**Post date:** [June 21, 2021, 2:59am UTC](https://support.prodi.gy/t/prodigy-doesnt-launch-or-die/4329/2 "2021-06-21T02:59:35Z")

</div>

Hi @sudarshan85 ,

Sorry for the delay getting back to you on this.

The fact that it doesn't exit with CTRL+C makes me suspicious. As a bit of background context, if a Python process is spending time within a C-compiled function, it won't check for keyboard interrupts --- the keyboard interrupt signal is only checked when control is returned to the Python interpreter.

So I wonder whether your recipe is busy working, and that's why it won't take connections and also won't exit cleanly. A particular possibility is that it's running out of memory.

Could you check the resource usage with `top` to see if it's busy computing during this time, and if the memory usage is staying under control? If you have `perf` on the machine, that would also be a good way to check what it's doing. Otherwise if you can install the `py-spy` utility, that's another way to see what's running.