Upgraded my network setup. Now having issues with certain devices
accessing a reverse proxy hosted on the same network.
reddit / selfhosted

----------------------------------------------------------------------
NoFeedback4007 · 2023-12-15 15:32

Hi!

I purchased a Unifi Express to replace my aging setup. I finally got
it installed, and I have a few devices that can't seem to access my
reverse proxy that's hosted on he same network, while some can. All
devices are on the same default network, except for the last example.

Example 1: Computer is hardwired. When loading my reverse proxy
websites, I get connection has timed out. When I disable eth and
connect via WiFi, it works. Same network.

Example 2: Wife's phone can't access locally hosted streaming app.
Connected to the same default network as the server. When I swap her
to the Guest network, she's able to connect just fine.

I searched the past couple of nights through google, and I can't seem
to find whats causing my issue. What am I doing wrong here?

I should note that I do have Pi-hole running and I don't believe that
is causing the issue. I tested my network to run whatever is default
with Unifi.

----------------------------------------------------------------------
Sgt_ZigZag · 2023-12-15 16:27

DNS. It's always DNS.

----------------------------------------------------------------------
NoFeedback4007 · 2023-12-15 16:34

Any idea on where I can start to fix it?

----------------------------------------------------------------------
warlock2397 · 2023-12-15 18:06

I don't think you can call it an upgrade in that case.

On a serious note: Check your DNS entries in Pi-Hole.

----------------------------------------------------------------------
Trixster82 · 2023-12-17 01:39

1. Could this also be NAT hair pinning on the firewall if the DNS is
pointing to the public IP?

2. Also I'd try flushing your DNS cache of the devices and seeing if
that fixes or breaks anything.

3. Try rebooting and reprovisioning the switches and WAPs in case any
weird old configs are sitting on them

4. DHCP or subnet changes and VLANs in order?

5. Is pihole set to only listen to specific subnets? If a docker, this
can reset if not configured correctly in the compose file.

6. Do you have a secondary DNS listed other than pihole (i.e.
everything works except internal routing DNS provided by pihole)?

7. Is pihole seeing the requests come in?

----------------------------------------------------------------------
NoFeedback4007 · 2023-12-18 03:18

1. I'm not familiar with hair pinning. Are you able to explain? My
friend mentioned this and he said this was his problem, but can't
remember how he fixed it.

2. Tried and no avail.

3. Also tried this.

4. DHCP and VLANs were set back up essentially how my old system was.
I took screenshots and set it back up the way I had them before the
new setup.

5. Pihole is running on a pi2, and has permit all origins since im
using VLANs

6. no seconary DNS listed. I attempted to use 8.8.8.8 for a while and
it still wasn't working.

7. Pihole is seeing the requests come in and is answering them from
pihole/unbound.

Thanks for replying. I do appreciate it.