I’ve just about got this Docker thing licked. After hundreds of hours, I finally get it, and my dusty millenial ass has joined the 21st century.
-but we have issues
==============================xxxx==============================
The environment:
I have multiple containers running on my local network, including photoprism, Kavita, and Filebrowser. I also installed Heimdall as a startpage. On the local network everything works great.
The entire goal of this project is to have these services accessible from outside the house, from my mobile devices but also with the ability to share links and files with friends.
==============================xxxx==============================
The problem:
Enter Tailscale. I tried port forwarding, having a domain, all that jazz, but it ended up being way too complicated. I don’t want just anyone to access my shit, I only want a handful to be able to use services of my choosing in accordance with the user permissions I set up for them. Tailscale was the first thing I tried that worked.
I added my docker instance to tailscale, and when you access the machine, you are correctly taken to my Heimdal start page. Unfortunately, when you click on the icons for my docker services, the browser gives you an “unable to connect” error.
Under my Tailscale admin panel, the services are listed along with their port and IP information. Heimdall (443) and Portainer(8000) are listed as https and http under “type”, as expected. The remaining services are listed as “other.” (the portainer link doesn’t work either)
-
Has anyone else dealt with this?
-
If this has to do with ports, is there an easy way to configure ports without having to re-run the images and make new containers?
I think…
You need to change the Heimdall urls to the the tailscale urls. I’ll update this post soon.
My old set up has openmediavault as the base system.
I installed tailscale directly to that base system. (The OS)
My old ip links in Heimdall stopped working.
From memory… You need to go to the tail scale website dashboard. Iirc by default you have some random numbers as your tailscale URL. The other option is to use their magic DNS which gives you random words as a URL. Either way you will need to edit you Heimdall links. So if it’s currently http://192.167.1.1:8096 you need to change it to http://buffalo-cow.tailscale:8096. (Or something to that effect.)
What I did was just duplicate my current Heimdall and used a different port number… Then change all the urls to the tailscale urls.
Your current containers should remain untouched aside from the the Heimdall one with the correct app urls.
Edit: I think an example of the tailscale URL with magic DNS enabled would be something like this. https://amelie-workstation.pango-lin.ts:8096
Except that the services are “unable to open” and “other” even from the tailscale admin panel. The top two services, heimdal and portainer, are the only ones with an “open” link.
edit: if I stop heimdall in Docker, the situation is the same, except no start page.
OP here’s a troubleshooting approach i would take:
-
ensure services can be reached locally, thus eliminating tailscale as a variable. test on the host itself as well as another device on the same network.
-
attempt connecting, with tailscale enabled, to the services directly. meaning, go to the hosts’s tailscale IP:port in a browser and NOT through heimdall
-
if the above work, then it’s an issue with heimdall. edit the config as previously mentioned to link the services to the host’s tailscale IP:port, or have two instances of heimdall - one for local and one for remote
-
Hmm… I’m not sure. If your making it to Heimdall and portainer I don’t see why the other containers wouldn’t work. I just remember having to redo my Heimdall links.
Is tailscale installed on the base operating system?
Tailscale is on both the base OS and I have the docker extension, which required the base OS install IIRC.
Fwiw I never used a tailscale docker. I just had it on the base OS.
Do these port numbers tell you anything at all? I’m very new to all of this.
The port numbers seem fine. They shouldn’t effect the issue you’re having to my knowledge.
I think I figured it out, just have to implement the fix. I think the problem is the lack of 443’s published by the containers. Looks like I may be able to modify the ports easily in Portainer.
