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

    Pfblocker (DNSBL) and android amazon app (android web viewer) issue "SOLVED"

    Scheduled Pinned Locked Moved pfBlockerNG
    20 Posts 16 Posters 18.8k 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.
    • S
      silverhair
      last edited by

      I used the posted whitelist above, and the Amazon app works.

      @thezfunk, where did you add your whitelist? 
      Under Firewall -> pfBlockerNG -> DNSBL there are two options, the "Custom Domain Whitelist" and the "TLD Whitelist". 
      Which did you use?

      After you've updated the list, you'll need to wait ten minutes for the cronjob to update the lists, or force the list to update manually.  Did you wait long enough?

      1 Reply Last reply Reply Quote 0
      • L
        lordbob75
        last edited by

        I'm having this issue as well.  Added the entire list posted a couple comments up by silverhair, but still closes the login screen constantly.

        Silverhair asked about which whitelist, I thought it was the Custom Domain Whitelist.  Should it be the TLD one instead?

        Edit:  Did not realize that the update didn't push changes and needed to reload it instead.  Able to log into the app now.  Thanks to Silverhair for the list.  May have to try removing lines one at a time until it stops working though.

        1 Reply Last reply Reply Quote 1
        • B
          BSA66
          last edited by

          I was just running into a similar issue (Amazon Android App not working)

          My shortly added Domain Whitelists are the following:

          .c.amazon-adsystem.com # Amazon Advertisements
          .d1ykf07e75w7ss.cloudfront.net # CNAME for (c.amazon-adsystem.com)
          .fls-eu.amazon.de
          .fls-eu.amazon.com # CNAME for (fls-eu.amazon.de)
          .gateway.prod.eu-west-1.forester.a2z.com # CNAME for (fls-eu.amazon.de)
          .endpoint.prod.eu-west-1.forester.a2z.com # CNAME for (fls-eu.amazon.de)
          .mads.amazon-adsystem.com # Amazon Adsystem Mads
          .amazon-adsystem.com # Amazon Adsystem MADS

          As you see it is a little bit unsorted what I track back to my whitelisting flow... You should not just copy & paste it as in your region and on your phone / setup / yet added Domains on the Whitelist it may work or even not work.

          The process is easy.

          • run your apps and keep about 5-10 secs after reload the DNSBL Alert Tab
          • check for potentially corresponding Domains
          • whitelist them**

          ** First I added them manually to the Domain Whitelist which did not work (I guess the CNAMEs might have been missing...)
          It is uncomfortable to whitelist them automatically by the + Sign as every Alert Tab Reload takes Ages to reload...
          But anyway, at least it was necessary for me to get the CNAMEs, too, as it did not seem to work without them.
          BTW this is also the reason why the List seems to be so unsorted, I added several before the automatic initiated Alert Tab Reload (and maybe the hidden but initiated Reload-DNSBL for adding the new Entries) accomplished.

          1 Reply Last reply Reply Quote 0
          • A
            aaronhong13
            last edited by

            Not sure if this is still an ongoing issue, but posting incase someone else finds this thread with the same question.

            Adding this fixed the app for me. No more "Something has gone wrong messages". If any other issues come up, I will update this post.

            DNSBL Whitelist
            .aan.amazon.com

            1 Reply Last reply Reply Quote 1
            • V
              viskalpiskal
              last edited by

              Old thread, created an account to help others
              from uk here, managed to fix it as per BSA66 suggestion, loading the app and looking at the DNSBL Alert tab for my phone

              saw, z.moatads.com
              and then whitelisted it
              now have several whitelist domains
              z.moatads.com # z.motads
              www.z.moatads.com # z.motads
              wildcard.moatads.com.edgekey.net # CNAME for (z.moatads.com)
              e13136.g.akamaiedge.net # CNAME for (z.moatads.com)

              Hopefully this will fix the problem for you.

              1 Reply Last reply Reply Quote 0
              • J
                jjneff
                last edited by

                Hey all,
                I read this somewhere else for a non-pfsense oriented fix. If your phone allows it, change the app settings to only allow it to use cell data. Obviously this doesn't help if you HAVE to use wifi, but it also doesn't help your network's security to whitelist all these url's for the sake of one device/app imo. I figured it would be a helpful consideration for those it may apply to.

                1 Reply Last reply Reply Quote 0
                • B
                  bandit8623
                  last edited by

                  aan.amazon.com

                  is the 1 that needs to be added only to stop the uh oh in the amazon app

                  noplanN 1 Reply Last reply Reply Quote 1
                  • noplanN
                    noplan @bandit8623
                    last edited by

                    @bandit8623

                    true statement the only one needed to fix uh oh

                    aan.amazon.com

                    1 Reply Last reply Reply Quote 0
                    • G
                      GorillaMitts
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • P
                        pulsartiger
                        last edited by

                        I have this issue also with pfblocker and the Amazon app (Android). I whitelist the domains that I saw in the report log but I still have the dog screen come up stating "UH-OH Something went wrong on our end." What's odd is that this only happens when searching and it only happens when searching certain terms. Has anyone found the exact domains to whitelist? (aan.amazon.com did not do it for me)

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