# Error: an attempt was made to access a socket in a way forbidden by its access permissions

**URL:** <https://support.prodi.gy/t/error-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/2693>\
**Category:** Uncategorized\
**Tags:** solved, windows, server\
**Created:** [March 23, 2020, 9:18pm UTC](https://support.prodi.gy/t/error-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/2693 "2020-03-23T21:18:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [March 27, 2020, 10:53am UTC](https://support.prodi.gy/t/error-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/2693/7 "2020-03-27T10:53:34Z")

</div>

> [@annaakhil](#):
>
> I was able to access another port by editing in prodigy.json on the windows but was not able to access another port while trying in docker. the same thing I did in Docker also by editing prodigy.json but not able to access it.

Is the `prodigy.json` available in the right place in your Docker container? It looks like it's not being read correctly, since the server starts up on the default `localhost` with port ` 8080`.

In a containerised environment, it might be better to use the environment variables `PRODIGY_HOST` and `PRODIGY_PORT`. Alternatively, here's a starter dockerfile that uses a template for the `prodigy.json`: [Cloud deploy dockerfile](https://support.prodi.gy/t/cloud-deploy-dockerfile/1102)

---

_[View the full topic](https://support.prodi.gy/t/error-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/2693)._