this post was submitted on 18 Jan 2024
26 points (90.6% liked)

Selfhosted

40728 readers
633 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
26
Tailscale help needed (self.selfhosted)
submitted 11 months ago* (last edited 11 months ago) by butt_mountain_69420 to c/selfhosted
18 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] nickknack 5 points 11 months ago

OP here’s a troubleshooting approach i would take:

  1. 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.

  2. 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

  3. 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