Can't access my reverse proxy services inside my local network

  • OK, this will be my last attempt to fix this issue. After this I'm giving up. :)


    So, I have some docker containers running also via reverse proxy and that works great. I'm using swag and duckdns. They work fine on my phone over mobile network. But as soon as I try them on my local network, on my PC, it doesn't work. My OMV is on 192.168.0.111. If I ping any of those services from my PC I get this:

    Screenshot
    Mit Lightshot geschossen
    prnt.sc


    This is my duckdns docker:

    My swag:


    And for example my vaultwarden:


    my vaultwarden proxy-conf:



    I have a modem from my ISP, it's address is 192.168.1.1 and and WiFi router on 192.168.0.1


    Router:

    Screenshot
    Mit Lightshot geschossen
    prnt.sc

    Modem:

    Screenshot
    Mit Lightshot geschossen
    prnt.sc


    Any ideas what could be the issue here?

    • Neu
    • Offizieller Beitrag

    They work fine on my phone over mobile network. But as soon as I try them on my local network, on my PC, it doesn't work.

    "Hairpinning" could be the problem, depending on the features of your router. https://en.wikipedia.org/wiki/…anslation#NAT_hairpinning

    In my case I solved it with a local DNS server. For example pihole could work.

  • I tried finding that hairpining thing in my router, but no luck. My router is TP-Link WR1043ND. It should have NAT loopback by default.

    Hairpining is NAT loopback.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • Neu
    • Offizieller Beitrag

    It should have NAT loopback by default.

    I don't see anything here about NAT Loopback, but I could be wrong. https://www.tp-link.com/es/hom…-wr1043nd/#specifications


    It seems that that router supports OpenWRT. https://openwrt.org/toh/tp-link/tl-wr1043nd

    If you dare to install it, I would ask in the OpenWRT forum if that would solve your NAT Loopback problem.

    • Neu
    • Offizieller Beitrag

    I really don't dare to do it, I don't want to mess up my network even more.

    In that case pihole (or any other DNS server) could be the solution.

  • Exposing port 8445 of vaultwarden and not changing the reverse-proxy doesn't help.

  • In that case pihole (or any other DNS server) could be the solution.

    OK, I've deployed Pi-Hole. My compose is below. How can I now setup that DNS thingy?



    • Neu
    • Offizieller Beitrag

    I've deployed Pi-Hole. My compose is below. How can I now setup that DNS thingy?

    No idea, I've never used pihole but I guess you'll have everything you need here. https://pi-hole.net/

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!