Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Your phone’s hotspot likely doesn’t create a local network. The other problem is that Tailscale works by creating a secure tunnel between your client and your PC. Local devices won’t have access to this secure tunnel. You need to setup Tailscale directly on the client device you want to connect to your PC from for it to work.
Again I have tried to set it up directly, it fails every time. Tail scale has subnet routing for this very purpose, I just can't figure out what I am doing wrong on either one.
Subnet routing is generally far more complex than simply installing the client. If you aren't succeeding at one you're likely not going to succeed at the other.
I don't know the exact problem based on what you've described and I'm not going to promise I can solve it for you but I'm going to try to give you some tools you can use to help yourself a little and hopefully be able to better understand what is going wrong and that will help you understand what you can do about it. Don't get frustrated by this issue, this is a learning experience and this is a skill you need to invest in and develop so that you're not just blindly copy-pasting instructions from videos (which is a bad place to be)
Step 1: Figure out where your tailscale.sh actually is.
Once inconsistency I noticed in your description of what's going on is that you're attempting to run
tailscale.sh
but you're describing a path of/home/deck/documents/github/deck-tailscale.sh
not sure if this is just a typo or what but that describes a file calleddeck-tailscale.sh
which is not the same thing astailscale.sh
.I think the repository you've downloaded based on those instructions is called
deck-tailscale
however a repository is a folder full of files, and tailscale.sh is ONE of those files. That repository's name would probably be/home/deck/documents/github/deck-tailscale/
so if you're looking fortailscale.sh
inside that repository it will be/home/deck/documents/github/deck-tailscale/tailscale.sh
. (two tailscales in the full path, one for the repo and one for the file itself)You can verify all of these paths by using the
ls <path>
command, ls (that's L and S, not IS) means "list" and is similar thedir
command in Windows, it will show if the file you specify exists, or if it is a directory it will list all the contents of that directory. ls is a useful command to explore the directories and see which ones exist and which ones don't. You can work your way up the path to see where things are going wrong, for example, ifls /home/deck/documents/github/deck-tailscale/
does not exist, tryls /home/deck/documents/github/
and if that doesn't work tryls /home/deck/documents/
and so onSecond note: I notice your documents path is
/home/deck/documents
I don't have a steam deck in front of me to check, but my Linux system has a documents folder called/home/<me>/Documents
with a capital D. Paths on Linux are always case-sensitive. That means /documents is not the same thing as /Documents, which is not the same as /DOCUMENTS/ and if you attempt to use one when it's actually the other, the file will not be found. Make sure the capitalization is correct in the whole path.Step 2: Once you've located the correct path name of tailscale.sh you should be able to run it with:
sudo <full-path-to-tailscale.sh>
Good luck.
find / -name "tailscale.sh" 2>/dev/null ?
Or with mlocate:
locate tailscale.sh ?