# ERROR:Worker worker process died unexpectedly **URL:** \ **Category:** mediasoup libraries\ **Created:** [September 16, 2019, 5:12am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268 "2019-09-16T05:12:19Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 7, 2019, 9:18am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/41 "2019-10-07T09:18:03Z")
Any update after the code change? BTW let’s continue [here](https://github.com/versatica/mediasoup/issues/333) please. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 7, 2019, 1:31pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/42 "2019-10-07T13:31:17Z")
No crash yet after the last change but too early to decide (3 days past). > [@ibc](#): > > BTW let’s continue [here](https://github.com/versatica/mediasoup/issues/333) please. Okay 👍. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 7, 2019, 1:37pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/43 "2019-10-07T13:37:19Z")
Great, let me please how it goes on next days. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 7, 2019, 2:31pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/44 "2019-10-07T14:31:11Z")
Sure and one noob question. Does using TCP means we need to open also the TCP `minPort/maxPort` range on the server firewall or that’s for UDP only? ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 7, 2019, 2:36pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/45 "2019-10-07T14:36:58Z")
You must open both UDP and TCP ports in the min-max range you passed to the worker. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 7, 2019, 2:48pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/46 "2019-10-07T14:48:56Z")
Thanks. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 12, 2019, 8:41am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/47 "2019-10-12T08:41:38Z")
No crash after a week so it seems the bug has been fixed 😃 ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 13, 2019, 9:08am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/48 "2019-10-13T09:08:01Z")
Not really fixed since it should not have crashed before, and I do not yet why it did 🙂 By not sending DTLS BYE on transport closure (the code block you disabled) the crash does not happen, but that’s like loosing functionality just becase we cannot figure out where the bug is… ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 13, 2019, 12:42pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/49 "2019-10-13T12:42:17Z")
Now we have a clue at least, right? Let me know if we can go farther by doing more tests. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 14, 2019, 8:11am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/50 "2019-10-14T08:11:36Z")
Please let me know when you call `transport.close()` in server side. Do you call it when receiving an event “dtlsstatechange” with value “closed” or “failed”? Are you also calling `transport.close()` when the participant’s WS connection is closed by the participant? ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 14, 2019, 8:37am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/51 "2019-10-14T08:37:59Z")
I close peer transports on any type of user disconnection including normal exit, unexpected disconnect, etc. I do nothing with `dtlsstatechange`. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 14, 2019, 8:38am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/52 "2019-10-14T08:38:24Z")
ok thanks. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 14, 2019, 11:14am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/53 "2019-10-14T11:14:13Z")
@mkh could you please use the mediasoup GIT “devel” branch in your deployment? I’ve been trying to reproduce your crash with no success at all (without commenting the code block above). There are some tiny changes from “v3” to “devel” in that regards and may be the issue is fixed by those changes. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 14, 2019, 1:06pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/54 "2019-10-14T13:06:58Z")
Of course if you think that is safe to be used in production. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 14, 2019, 1:17pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/55 "2019-10-14T13:17:22Z")
“devel” branch has some bug fixes and includes transport-cc for bandwidth estimation, which works much better than REMB. We have heavily tested it in our demo environment. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 14, 2019, 2:07pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/56 "2019-10-14T14:07:00Z")
Very good. I’ll update the server tonight. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 14, 2019, 2:15pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/57 "2019-10-14T14:15:40Z")
Move or rename the current `node_modules/mediasoup` directory, clone the devel repo there and then run `npm install`. Is this all I need to do? ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [October 14, 2019, 2:21pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/58 "2019-10-14T14:21:41Z")
Yes. Just don’t forget to run `git checkout --track origin/devel` after cloning the repo and before running `npm install`. ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 14, 2019, 2:32pm UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/59 "2019-10-14T14:32:18Z")
👌 ---
**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\ **Post date:** [October 15, 2019, 4:41am UTC](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268/60 "2019-10-15T04:41:22Z")
The devel branch is setup and running. BTW by executing `npm i --production` I got the following warning so I had to run the `make` manually: `npm WARN lifecycle mediasoup@3.2.5~postinstall: cannot run in wd mediasoup@3.2.5 run-script-os (wd=/var/conference/server/node_modules/mediasoup-devel)` [Previous page](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268.md?page=2) [Next page](https://mediasoup.discourse.group/t/error-worker-worker-process-died-unexpectedly/268.md?page=4)