# \[Resolved\] Recent change breaks connectivity in Docker (+ non-Docker)
**URL:** https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498
**Category:** Development
**Created:** [November 3, 2019, 9:33pm UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498 "2019-11-03T21:33:24Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@bertieb](https://meta.discourse.org/u/bertieb)
#### Post date: [November 3, 2019, 9:33pm UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498/1 "2019-11-03T21:33:25Z")
I’ve had issues with [being completely unable to connect to a Dockerised dev instance](https://meta.discourse.org/t/beginners-guide-to-install-discourse-for-development-using-docker/102009/64).
I thought I’d give the non\_docker dev version a try. From there I could connect to localhost but not any other address. I then saw [featheredtoast’s comment](https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-ubuntu-for-development/14727/327) about changing the defaults in dev environments to ensure that they bind to localhost ([64d51a](https://github.com/discourse/discourse/commit/4935c9f1f8db54312d8343a278c23cb0d3f6b61b)). So on the Docker instance I checked out the rev prior to that, and I can connect to the Dockerised instance!
## Steps to replicate:
1. Follow [Beginners Guide to Install Discourse for Development using Docker](https://meta.discourse.org/t/beginners-guide-to-install-discourse-for-development-using-docker/102009)
2. Connections to port 9292 (localhost, 127.0.0.1, ::1, or by IP) are immediately closed
3. `git checkout 4935c9f1f8db54312d8343a278c23cb0d3f6b61b` ([prior rev](https://github.com/discourse/discourse/commit/4935c9f1f8db54312d8343a278c23cb0d3f6b61b))
4. Rebuild dev environment and run
5. Connections to port 9292 work as expected
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 4, 2019, 1:53am UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498/2 "2019-11-04T01:53:31Z")
Sure, this is a great catch, addressed here:
[https://github.com/discourse/discourse/commit/ff33899323f71ca750c0e555ce8f71d8896a3b3a](https://github.com/discourse/discourse/commit/ff33899323f71ca750c0e555ce8f71d8896a3b3a)
If you wish to globally expose the ports from the container to the network (default off) use.
```plaintext
d/boot_dev -p
```
---
### Author:  [@bertieb](https://meta.discourse.org/u/bertieb)
#### Post date: [November 4, 2019, 7:40am UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498/3 "2019-11-04T07:40:24Z")
Thanks @sam 👍
Can confirm that with latest master (2 commits after yours at time of writing) connectivity seems to work as intended.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 5, 2019, 7:06am UTC](https://meta.discourse.org/t/resolved-recent-change-breaks-connectivity-in-docker-non-docker/132498/4 "2019-11-05T07:06:32Z")
This topic was automatically closed after 29 hours. New replies are no longer allowed.