Hmm… I’m not sure. It 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.
Comment on Tailscale help needed
butt_mountain_69420@lemmy.world 10 months agoExcept 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.
ULS@lemmy.ml 10 months ago
butt_mountain_69420@lemmy.world 10 months ago
Tailscale is on both the base OS and I have the docker extension, which required the base OS install IIRC.
ULS@lemmy.ml 10 months ago
Fwiw I never used a tailscale docker. I just had it on the base OS.
nickknack@lemmy.world 10 months ago
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