# Connecting to same Dradis instance for real time collaboration **URL:** \ **Category:** Community Edition\ **Created:** [August 29, 2016, 7:40am UTC](https://discuss.dradis.com/t/connecting-to-same-dradis-instance-for-real-time-collaboration/353 "2016-08-29T07:40:48Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![etd](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dradis.com/etd/32/5_2.png) [@etd](https://discuss.dradis.com/u/etd)\ **Post date:** [August 30, 2016, 7:57am UTC](https://discuss.dradis.com/t/connecting-to-same-dradis-instance-for-real-time-collaboration/353/2 "2016-08-30T07:57:14Z")
Hi @aksh7sharma, By default Dradis binds to the local loopback interface so others in the network don’t have access to it. You just need one of you to bind to an external interface (one that others can ping to) and then everyone will be able to work on the same instance. This is done through the `-b` parameter as explained here: > [@Web display not work](https://discuss.dradis.com/t/web-display-not-work/316/2): > > Hi @trasla, This line: tcp 0 0 127.0.0.1:3000 0.0.0.0:\* LISTEN 5581/ruby Makes me think the server is binding to 127.0.0.1 meaning you can only connect to it from within the same host. If you want to bind to other network interfaces (e.g. to access from outside a VM for example), pass the -b command, for example: bundle exec rails server -b 0.0.0.0 If using running from a Git clone. Or ./dradis-webapp -b 0.0.0.0 If using the packages. HTH, Daniel … HTH, Daniel --- _[View the full topic](https://discuss.dradis.com/t/connecting-to-same-dradis-instance-for-real-time-collaboration/353)._