# Firefox pipeToRouter problems? **URL:** \ **Category:** mediasoup libraries\ **Created:** [November 5, 2020, 7:33pm UTC](https://mediasoup.discourse.group/t/firefox-pipetorouter-problems/1995 "2020-11-05T19:33:34Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [November 6, 2020, 1:15am UTC](https://mediasoup.discourse.group/t/firefox-pipetorouter-problems/1995/2 "2020-11-06T01:15:34Z")
> [@aguynamedchris](#): > > Additional notes: > > 1. If James is producing but only router1 is used (for producers and consumers), Firefox works fine. > 2. If James is NOT producing / part of the broadcast, and is just viewing Kim+Natalie, all is well (he can see/hear them). > > I am at a loss as to how the browser could be a factor here…any ideas? I remember some issues in Firefox when creating two PeerConnections in the same website and the remote endpoint uses different DTLS certificates. So if you use two mediasoup Routers in **different** mediasoup Workers, each Worker will have its own random DTLS certificate. NOTE: If “James” is not producing, then the `sendTransport` does not even connect ICE+DTLS to mediasoup. That happens once the first Producer (or DataProducer) is created. So this explains the issue if my above suspicion is true. So: 1. Ensure ICE and DTLS connects in both `sendTransport` and `recvTransport` when running Firefox in your failing scenario. This is critical, please don’t do bypass of this step. If I’m right one of those transports will fail at DTLS level. 2. Create a TLS certificate and use it in your mediasoup Workers, so all Workers will use the same one and Firefox may not complain. 3. If any of those is true, please comment here but also report the issue in the Firefox issue tracker. --- _[View the full topic](https://mediasoup.discourse.group/t/firefox-pipetorouter-problems/1995)._