Beiträge von speedy9

  • Deploying ngrok in Docker to externalize access

    I think I sorted this our initially. It works, try yourself if you can access my PiHole login page: https://ink_was_here


    EDIT:

    Solution: ngrok Docker must be joined to the same network where another Docker container is connected. In my case it was PiHole network where there was no DHCP so I had to assign a static IP (.241 here) for ngrok container with the command:

    docker run --net=pihole_network --ip=192.168.31.241 -it -e NGROK_AUTHTOKEN=<my_ngrok_token_here> ngrok/ngrok:latest http 192.168.31.240:80

  • Deploying ngrok in Docker to externalize access

    Zitat von chente

    I have no idea how exactly ngrok works. But I assume that you will need access from the outside to some public port on your network.

    If your ISP has provided you with internet access behind a NAT (CGNAT or similar) this will be impossible. You need to have a public IP.

    It's exactly why I need to use ngrok or portmap.io. It is possible with these services to access internal resources without public IP.

    It's a matter of setting this up correctly in Docker.

  • Deploying ngrok in Docker to externalize access

    Hi

    I'm behind a dual NAT with no external internet IP. After reading a lot about port forwarding and setting up VPNs I decided to try ngrok to externalize access to my OMV and other network resources. But I'm a bit stuck at the very beginning :D I ran ngrok in Docker with:

    docker run --net=host -it -e NGROK_AUTHTOKEN=<my token here> ngrok/ngrok:latest 192.168.31.240 80

    to see if I will be able to access my PiHole web interface.

    PiHole is hosted in another Docker container with IP from my local network.

    Unfortunately ngrok gives me this only:

    There is something wrong with traffic routing for sure but I'm not experienced with Dockers and Linux at all so having troubles configuring this. How should I set up Docker network? I currently have following networks, the last one is for PiHole: