• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Please match the requested format on Alias Error

Scheduled Pinned Locked Moved Firewalling
8 Posts 6 Posters 2.5k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    genesislubrigas
    last edited by Sep 23, 2016, 1:55 AM

    I have created this aliasname AllowedToSocialMedia but then when I applied it to firewall I get this error "Please match the requested format"
    I am using the latest version of pfsense 2.3.2

    Attached is the screenshot.
    allowedtosocialmedia.png
    allowedtosocialmedia.png_thumb

    1 Reply Last reply Reply Quote 0
    • N
      nandattebayu
      last edited by Sep 23, 2016, 7:52 AM

      try on other web browsers

      1 Reply Last reply Reply Quote 0
      • R
        RonpfS
        last edited by Sep 23, 2016, 5:32 PM

        @jimp:

        • Navigate to System > Package Manager, Available Packages tab
        • Install the System Patches package
        • Navigate to System > Patches
        • Click + Add New Patch
        • Enter the Description: Chrome Bug Workaround
        • Enter the URL/Commit ID: 83469e50681bf1ab0388e5cb756d5198b7f705f4
        • Click Save
        • Click Fetch
        • Click Apply

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 0
        • M
          MontTech
          last edited by Oct 11, 2016, 4:59 PM

          Ron,

          Thanks for the fix!

          1 Reply Last reply Reply Quote 0
          • D
            Derelict LAYER 8 Netgate
            last edited by Oct 11, 2016, 5:13 PM

            At this point just upgrade to 2.3.2_1. It includes that patch.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • M
              MontTech
              last edited by Oct 11, 2016, 5:16 PM

              Yeah we're trying to…Have over 100 to do.  :o

              1 Reply Last reply Reply Quote 0
              • T
                thallam08
                last edited by Oct 12, 2016, 8:46 AM

                I've updated and it looks like 2.3.2_1 only fixes this bug on some pages.  The IPSEC VPN configuration pages still have it.
                Unfortunately 2.3.2_1 seems to introduce another bug.  I can no longer set the destination port for a rule after upgrading.  Could set it before.  Using another browser does not fix this one.

                1 Reply Last reply Reply Quote 0
                • D
                  Derelict LAYER 8 Netgate
                  last edited by Oct 12, 2016, 5:38 PM

                  Destination port on what rule where? What's the URL on the firewall? what's the error you receive?

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received