# Prodigy refused to connect

**URL:** <https://support.prodi.gy/t/prodigy-refused-to-connect/6500>\
**Category:** Uncategorized\
**Created:** [April 21, 2023, 4:50am UTC](https://support.prodi.gy/t/prodigy-refused-to-connect/6500 "2023-04-21T04:50:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bordeengg](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@bordeengg](https://support.prodi.gy/u/bordeengg)\
**Post date:** [April 21, 2023, 4:50am UTC](https://support.prodi.gy/t/prodigy-refused-to-connect/6500/1 "2023-04-21T04:50:47Z")

</div>

Prodigy after installation, opening it on the browser shows connection reset by peer with closing connection. on the browser it shows - refused to connect

---

<div class="post-metadata">

**Author:** ![ryanwesslen](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ryanwesslen/32/2969_2.png) [@ryanwesslen](https://support.prodi.gy/u/ryanwesslen)\
**Post date:** [April 21, 2023, 12:21pm UTC](https://support.prodi.gy/t/prodigy-refused-to-connect/6500/2 "2023-04-21T12:21:50Z")

</div>

hi @bordeengg!

Thanks for your message and welcome to the Prodigy community 👋

Can you provide some additional details?

- What command were you running? Was it happening for all recipes or specific ones? Was it a custom recipe?
- How were you running it -- locally on your own machine, on a remote server, on a cloud, etc?
- Are there any firewalls / are you sure that your 8080 port is accessible?
- Have you modified any of the [configuration](https://prodi.gy/docs/install#config) settings?

Depending on your setup, you may need to set your `host`:

> [@Connection refused from remote machine.](https://support.prodi.gy/t/connection-refused-from-remote-machine/3181):
>
> After installing prodigy on the Ubuntu server, I can use prodigy on the server machine through [http://localhost:8080](http://localhost:8080). But when I want to use prodigy from a remote machine through such as [http://192.168.1.242:8080](http://192.168.1.242:8080)(in my case, server and client are both in the company's intra-network), I got an error message “ERR\_CONNECTION\_REFUSED” on the chrome browser.