Pi hole and Alexa

Problem

I tried now everything migrating from Raspberry Pi to a laptop and installed Ubuntu, but my Alexa is still not able to connect to my pi-hole. For clearness. I setuped my pihole machine over LAN. Then I created a hotspot with my pi-hole machine. 3 IoT devices are able to connect to my pi-hole over the provided hotspot (and have fully internet connection). Just alexa refuses to connect. If I try on a other hotspot like my other Phone or my home wifi it works flawlessly.

Expected Behaviour:

From my perspective, I do not see, why it does not connect to my hotspot.

Remark: I do not have any filterlist on my pi-hole (I wanted to be sure that everything is allowed).

Something stuck with me from reading somewhere a long while back to disable IPv6 but cant remember where and why.
Just did a search:

Configure your backend DHCP server to provide only IPv4 addresses. Disable IPv6 addresses.

EDIT: Oh that same page shows a nice list of domains for whitelisting:

|443|TCP|All of the following URLs:

* https://pindorama.amazon.com:443
* https://firs-ta-g7g.amazon.com/FirsProxy:443
* https://todo-ta-g7g.amazon.com/FionaTodoListProxy:443
* https://guipitan.amazon.com:443
* https://det-ta-g7g.amazon.com/DeviceEventProxy:443
* https://device-metrics-us.amazon.com/metricsBatch:443

EDIT2:

pi@ph5b:~ $ xargs -n 1 pihole -q <<< 'pindorama.amazon.com firs-ta-g7g.amazon.com todo-ta-g7g.amazon.com guipitan.amazon.com det-ta-g7g.amazon.com device-metrics-us.amazon.com'
  [i] No results found for pindorama.amazon.com within the adlists
  [i] No results found for firs-ta-g7g.amazon.com within the adlists
  [i] No results found for todo-ta-g7g.amazon.com within the adlists
  [i] No results found for guipitan.amazon.com within the adlists
  [i] No results found for det-ta-g7g.amazon.com within the adlists
 Match found in https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts:
   device-metrics-us.amazon.com

To permantly whitelist them all:

pihole -w pindorama.amazon.com firs-ta-g7g.amazon.com todo-ta-g7g.amazon.com guipitan.amazon.com det-ta-g7g.amazon.com device-metrics-us.amazon.com

To remove the whitelisting again:

pihole -w -d pindorama.amazon.com firs-ta-g7g.amazon.com todo-ta-g7g.amazon.com guipitan.amazon.com det-ta-g7g.amazon.com device-metrics-us.amazon.com

FYI:

$ pihole -w -h
Usage: pihole -w [options] <domain> <domain2 ...>
Example: 'pihole -w site.com', or 'pihole -w site1.com site2.com'
Whitelist one or more domains

Options:
  -d, --delmode       Remove domain(s) from the whitelist
  -nr, --noreload     Update whitelist without reloading the DNS server
  -q, --quiet         Make output less verbose
  -h, --help          Show this help dialog
  -l, --list          Display all your whitelistlisted domains
  --nuke              Removes all entries in a list
  --comment "text"    Add a comment to the domain. If adding multiple domains the same comment will be used for all

Just tried out and did not worked.
If a enable the rules from amazon (especisally the ports) I lose internet on my other devices!

EDIT! If I use the whitelist:

I get this:

 Match found in exact whitelist
   pindorama.amazon.com
 Match found in exact whitelist
   firs-ta-g7g.amazon.com
 Match found in exact whitelist
   todo-ta-g7g.amazon.com
  [i] No results found for guipitan.amazon.com within the adlists
 Match found in exact whitelist
   det-ta-g7g.amazon.com
 Match found in exact whitelist
   device-metrics-us.amazon.com

Follow/tail the Pi-hole logs live with below and check what gets blocked from the Alexa IP when you try to connect it to network:

pihole -t

Oh ps, do you know if you have IPv6 connectivity?

If so, did you try disabling IPv6 support (EDIT: for the LAN part only if possible) on the router already?

When I test on my pi-holes wifi It says no IPv6 detected!
When I use on my lan on my browser it shows me a IPv6!

EDIT: if I live watch with pihole -t the alexa apps makes calls to amazon.com but It does not succeed to coneect.

d7ae3d206ce5366b0f0105dc74e8b013274baf9c15fd9588c12a576fa3ac95c.us-east-1.prod.service.minerva.devices.a2z.com is 54.196.171.111
Sep  9 23:55:54: reply d7ae3d206ce5366b0f0105dc74e8b013274baf9c15fd9588c12a576fa3ac95c.us-east-1.prod.service.minerva.devices.a2z.com is 35.153.12.140
Sep  9 23:55:54: reply d7ae3d206ce5366b0f0105dc74e8b013274baf9c15fd9588c12a576fa3ac95c.us-east-1.prod.service.minerva.devices.a2z.com is 54.87.17.38
Sep  9 23:55:54: reply d7ae3d206ce5366b0f0105dc74e8b013274baf9c15fd9588c12a576fa3ac95c.us-east-1.prod.service.minerva.devices.a2z.com is 34.198.88.164
Sep  9 23:55:54: reply d7ae3d206ce5366b0f0105dc74e8b013274baf9c15fd9588c12a576fa3ac95c.us-east-1.prod.service.minerva.devices.a2z.com is 54.164.11.104
Sep  9 23:55:54: query[A] kinesis.eu-west-1.amazonaws.com from 10.42.0.230
Sep  9 23:55:54: forwarded kinesis.eu-west-1.amazonaws.com to 8.8.4.4
Sep  9 23:55:54: reply kinesis.eu-west-1.amazonaws.com is 99.80.34.145

And then it fails. FYI my .230 is my device which is using: alexa

Do you mean that IPv6 test link showed IPv6 connectivity?
If so, you can assume the Alexa also does if it supports IPv6.

I dont know why below is documented:

But its worth a try to disable IPv6 support on the router for that LAN part only.
But but but have you checked already following the logs live when you hookup the Alexa to your network?

I dont see any blocked by Pi-hole in that log snippet.

On my pi-hole? Or my other network?

Edit: I disabled the ipv6, nothing changed! :confused:

Below is still not clear to me?

If have IPv6 support upstream, the router/AP where Alexa is conneted to.

After disabling, try reconnecting the Alexa to network.
I'm outa ideas.

Okay I am pretty sure, the cause is the app with the pihole! Not the network settings...

Solution: I figured out that the hotspot has to be shared ip4! That solved my issue!

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.