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

    Squid and s3.amazonaws.com problem

    Scheduled Pinned Locked Moved Cache/Proxy
    1 Posts 1 Posters 768 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.
    • J
      jacekr
      last edited by

      hi all,

      I'm having strange problem with Squid and s3.amazonaws.com on my pfsense.

      I have configured the firewall in the way, that there is a group of trusted URLs, where proxy should not be required and the rest should be rejected: (to force users to use proxy)

      IPv4 TCP    LAN net    *        TrustedURLs      Web        *      none (pass selected hosts from the TrustedURLs alias)
      IPv4 TCP    LAN net    *        *                      Web        *      none (reject all other calls)

      The TrustedURLs has some hosts like:

      www.abcd.com
      www.efgh.com
      etc.

      it works perfectly for all the hosts listed there, but when I want to add s3.amazonaws.com (one if the app is using it for the images), it just doesn't work, it is being ignored and it hits the reject rule.
      Even if I add a rule like allowing the s3.amazonaws.com IP, it will hit the reject rule.

      Did anyone of you experience similar?

      Regards
      Jacek

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.