Do these port numbers tell you anything at all? I’m very new to all of this.
Comment on Tailscale help needed
ULS@lemmy.ml 1 year ago
I think…
You need to change the Heimdall urls to the the tailscale urls. I’ll update this post soon.
butt_mountain_69420@lemmy.world 1 year ago
ULS@lemmy.ml 1 year ago
The port numbers seem fine. They shouldn’t effect the issue you’re having to my knowledge.
butt_mountain_69420@lemmy.world 1 year ago
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.
butt_mountain_69420@lemmy.world 1 year ago
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.
nickknack@lemmy.world 1 year 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
ULS@lemmy.ml 1 year ago
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.
butt_mountain_69420@lemmy.world 1 year ago
Tailscale is on both the base OS and I have the docker extension, which required the base OS install IIRC.
ULS@lemmy.ml 1 year ago
Fwiw I never used a tailscale docker. I just had it on the base OS.