I’m hoping someone can help me figure out what I’m doing wrong.

I have a VM on my local network that has Traefik, 2 apps (whomai and myapp), and wireguard in server mode (let’s call this VM “server”). I have another VM on the same network with Traefik and wireguard in client mode (let’s call this VM “client”).

  • both VMs can can ping each other using their VPN IP addresses
  • wireguard successfully handshakes
  • I have myapp.mydomain.com as a host override on my router so every computer in my house points it to “client”
  • when I run curl -L --header 'Host: myapp.mydomain.com' from the myapp container it successfully returns the myapp page.

But when I browse to http://myapp.mydomain.com I get “Internal Server Error”, yet nothing appears in the docker logs for any app (neither traefik container, neither wireguard container, nor the myapp container).

Any suggestions/assistance would be appreciated!

  • Mike Wooskey@lemmy.d.thewooskeys.comOPEnglish
    1·
    7 months ago

    Thanks for helping, @lemmyvore@feddit.nl.

    I’m browsing from my laptop on the same network as promox: 192.168.1.0/24

    The tunnel is relevant in that my ultimate goal will be to have “client” in the cloud so I can access my apps from the world while having all traffic into my house be through a VPN.

    The VM’s IPs are 192.168.1.50 (“server”) and 192.168.1.51 (“client”). They can see everything on their subnet and everything on their subnet can see them.

    Everything is using my router for DNS, and my router points myapp.mydomain.com and whoami.mydomain.com to “client”. And by “everything” I mean all computers on the subnet and all containers in this project.

    Both VMs and my laptop resolve myapp.mydomain.com and whoami.mydomain.com to 192.168.1.51, which is “client”, and can ping it.

    • lemmyvore@feddit.nlEnglish
      1·
      7 months ago

      Is the browser also using the LAN router for DNS? Some browsers are set to use DoT or DoH for DNS, which would mean they’d bypass your router DNS.

      Do you also get “Internal Server Error” if you make the request with curl on the CLI on the laptop?

      How did you check that mydomain is being resolved correctly on the laptop?

      What do you get with curl from the other VM, or from the router, or from the host machine of the VM?

      • Mike Wooskey@lemmy.d.thewooskeys.comOPEnglish
        0·
        6 months ago

        Thanks so much for helping me troubleshoot this, @lemmyvore@feddit.nl!

        Is the browser also using the LAN router for DNS? Some browsers are set to use DoT or DoH for DNS, which would mean they’d bypass your router DNS.

        My browser was using DoH, but I turned it off and still have the same issue.

        Do you also get “Internal Server Error” if you make the request with curl on the CLI on the laptop?

        Yes, running curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51 on the laptop results in “Internal Server Error”.

        How did you check that mydomain is being resolved correctly on the laptop?

        ping whoami.mydomain.com hits 192.168.1.51.

        What do you get with curl from the other VM, or from the router, or from the host machine of the VM?

        From the router:

        Shell Output - curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0-
100    17  100    17    0     0   8200      0 --:--:-- --:--:-- --:--:-- 17000

100    21  100    21    0     0    649      0 --:--:-- --:--:-- --:--:--   649
Internal Server Error

        From the wireguard client container on the “client” VM:

        curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
Internal Server Error

        From the traefik container on the “client” VM:

        $ curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
Internal Server Error

        From the “client” VM itself:

        # curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
Internal Server Error

        From the wireguard container on the “server” VM:

        # curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
Internal Server Error

        From the traefik container on the “server” VM (This is interesting. Why can’t I ping from this traefik installation but a can from the other? But even though it won’t ping, it did resolve to the correct IP):

        $ ping whoami.mydomain.com
PING whoami.mydomain.com (192.168.1.51): 56 data bytes
ping: permission denied (are you root?)

        From the “server” VM itself:

        # curl -L -k --header 'Host: whoami.mydomain.com' 192.168.1.51
Internal Server Error
        • Mike Wooskey@lemmy.d.thewooskeys.comOPEnglish
          1·
          6 months ago

          Also, just to make sure the app is indeed running, I curled it from it’s own container (I’m using myapp here instead of whoami, because whoami doesn’t have a shell):

          $ curl -L -k --header 'Host: myapp.mydomain.com localhost:8080

          I can’t seem to display html tags in this comment, but the results are the html tags for the web page for the app - so the app is up and running