This would suggest a networking rather than a Pi-hole issue.
Most likely, your router there is not providing a route from/to your Pi-hole machine to/from your network.
You should check your router for possible reasons why it wouldn't route packets to your Pi-hole machine.
We've seen a similar report only recently where a router with enabled wifi client isolation was the cause.
EDIT:
I've stripped the bogus http links from your above ip result and reformatted it for better readability.
That made me notice that you've assigned the same IP address to both your eth0 and wlan0 interfaces. As mentioned in the link I've shared above, this will also prompt routing issues. Make sure that every interface carries an IPv4 address unique not only on that machine, but in your entire network.
Alternatively, you could consider to disable your wlan0 interface altogether, provided you don't need it for services other than Pi-hole (also saves a tad bit of power).