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

silverhair

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?

lordbob75

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.

BSA66

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.

aaronhong13

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

viskalpiskal

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.

jjneff

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.

bandit8623

aan.amazon.com

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

noplan

@bandit8623

true statement the only one needed to fix uh oh

aan.amazon.com

GorillaMitts

This post is deleted!

pulsartiger

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)