Bobcares

How to add Plex to pfSense Firewall

by | Oct 14, 2023

Learn how to add Plex to the pfSense Firewall. Our pfSense Support team is here to help you with your questions and concerns.

How to add Plex to pfSense Firewall

If you are looking for a way to get Plex Media Server to work through your pfSense firewall, you have come to the right place.

How to add Plex to pfSense Firewall

In this scenario, we must create firewall rules to permit network traffic. Plex usually uses certain ports for its different services. Hence, we need to create rules for these ports.

Let’s take a look at how to get this done:

  1. To begin with, we have to log in to our pfSense web interface.
  2. Then, create an alias that includes the Plex-related ports. This makes it easier to manage rules and update them later. So head to Aliases under Firewall and click Add to create a new alias.
  3. Next, enter a name for the alias and choose Ports as the Type.
  4. We have to enter the Plex-related ports separated by spaces or commas in the Ports field.
    For Plex, this usually includes TCP ports 32400 and other ports we may use for media streaming or remote access.

  5. Then, it is time to save the alias.
  6. After that, we must create a port forwarding rule to allow external traffic to reach our Plex Media Server. So head to Firewall > NAT > Port Forward and click Add.
  7. Now, we have to configure the rule as seen below:
    • Interface: Select the WAN interface.
    • Protocol: Choose TCP.
    • Source: Leave this as “any”.
    • Destination: Select “Invert match” and enter the alias we created earlier in the “Port” field.
    • Redirect Target IP: Enter the LAN IP address of the Plex server.
    • Redirect Target Port: Enter the Plex server’s port
  8. Then, save the port forwarding rule.
  9. After that, we have to create a firewall rule to allow the traffic from the WAN to the LAN where our Plex server resides. So, head to Rules under Firewall and select the WAN interface.
  10. Then, click Add to create a new rule.
  11. We have to configure the rule as seen here:
    • Action: Allow
    • Interface: WAN
    • Address Family: IPv4
    • Protocol: TCP
    • Source: Any
    • Destination: Type the LAN IP address of the Plex server.
    • Destination Port Range: Enter the same Plex-related ports mentioned in the alias or port forwarding rule.
  12. Finally, save the firewall rule.
  13. Once we create the port forwarding and firewall rules we have to click the “Apply Changes” button at the top of the pfSense web interface.

After the above steps, we will be able to access Plex Media Server remotely with our WAN IP address or domain name followed by the Plex port number.

Furthermore, we have to make sure our Plex server is configured correctly to allow remote access and is signed in to our Plex account.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to add Plex to the pfSense Firewall.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF