localhost refused to connect - worked initially, but not anymore

[ryanwesslen]

hi @rstr!

Thanks for the background.

That's good that Prodigy was installed correctly so you can begin using Prodigy via terminal.

@rstr

The Open Prodigy icon and Open Prodigy Docs icon are there, but when I click Open Prodigy, it opens a prodigy tab but the message is the same, localhost refused to connect.

Someone had success with to modify the host on the prodigy.json to "0.0.0.0":

Localhost refused to connect

I have a new update. I was able to expose the port and access it from my local machine. I was exposing port 80 which means the webserver needs to run on port 80 but the tricky part was getting it to not run on localhost. I think that because it's a VM, it needs to run on 0.0.0.0 rather than localhost. When I try to specify that within prodigy.json or the env var PRODIGY_HOST, I enter "0.0.0.0" and it tries to run the server on "0.0.0.0":80 - which obviously isn't right. I need it to run on 0.0.0…

If this is successful, then you will want to follow these instructions to modify your prodigyConfig:

Localhost refused to connect

Hi @Joshmantova , to configure the Jupyterlab Prodigy extension, (in Jupyterlab) head to "Settings" > "Advanced Settings Editor" > "Prodigy Jupyter Extension" then update the prodigyConfig with the URL you're checking. It might also be better if you enable HTTP (or HTTPS) traffic in your Google Cloud VM (or the VM where the Vertex AI notebook runs). Not sure what you meant by this. Where do you see that "0.0.0.0":80 is being run? For reference, my prodigy.json config shows this: { "port": 8…

Last, could there be some AWS firewall or rules to modify?

Serving a manual annotation project within an internal network

Yes, I would expect that to work. If you give it a try, what happens? Some other details you might want to think about are whether the ports are blocked by firewalls on the network. For default AWS and GCE instances, there may be default rules on the network you need to configure. You might find it easiest to leave it on port 80, while using the local network IP.

If this doesn't help, since you were able to get it to run one time, it may be worth a try to rebuild your instance. Hopefully it isn't too inconvenient.

Let us know if you come up on any further questions or if you're able to get this to work!