On Aug 14th 11 PM ET/Aug 15th 03:00 UTC, due to scheduled Firefox Account server maintenance, users may not be able to sign in or create a new subscription. This is expected to last approximately 30 minutes. Status updates can be found at https://status.vpn.mozilla.org or https://status.relay.firefox.com.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox Ports Outbound: 50000 - 65535

  • 1 baphendule
  • 1 inale nkinga
  • 7 views
  • Igcine ukuphendulwa ngu cor-el

more options

Why does Firefox use dynamic ports in the 50K+ range when I use it to browse the web?

I have included screen shots with netstat -AB as well as currports.

Furthermore, if I set a rule in Windows Firewall blocking outbound traffic on ports 50000 - 65535, it breaks DNS with Firefox, even though 53 UDP is open.

I'm not overly concerned with any connection that is localhost / 127.0.0.1.

I've tried prohibiting these ports by modifying user.js - No impact, only works if I implicitly call out the port (example.com:55000)

What do? Why is FF using these ports?

Why does Firefox use dynamic ports in the 50K+ range when I use it to browse the web? I have included screen shots with netstat -AB as well as currports. Furthermore, if I set a rule in Windows Firewall blocking outbound traffic on ports 50000 - 65535, it breaks DNS with Firefox, even though 53 UDP is open. I'm not overly concerned with any connection that is localhost / 127.0.0.1. I've tried prohibiting these ports by modifying user.js - No impact, only works if I implicitly call out the port (example.com:55000) What do? Why is FF using these ports?
Ama-screenshot ananyekiwe

All Replies (1)

more options