Not yet but I plan to. Just haven’t gotten around to setting it all up yet.

Instead of 8080:8080 port mapping you do 127.0.0.1:8080:8080

To my knowledge there is no such thing available however you have just enlightened me about TS6’s featureset. It sounds like it is the exact solution you are asking for (and one I’m going to immediately try out myself.)

So you’re going to start backing it up immediately then right? Right?!?!?

I don’t pay any mind to example compose files. My are all quite custom anyway. Only thing that matters is paying attention to changelogs and watching for breaking changes.

It’s a learning exercise

Then crack open the documentation and learn how to actually write and use ansible

Thanks for the followup. This one is actually exactly what I was think about building. I just stood it up and it works perfectly.

You’re requirements are too vague as “lots of apps/VMs” doesn’t describe the expected load. Overall though if you want small just build a mini-ITX system. Then you can put in any x86 chip that fits your needs.

Can’t say I’ve run into a need for such consideration yet. Excluding stacks explicitly meant to work together to some degree most of my services are an island to themselves and I like it that way. Then as far as notifications are concerned pretty much every supports at least email or ntfy.sh.

Thanks for the warning. To the blocklist it goes.

I’ll have to check this out. I’ve been meaning to rig up a container for this same scenario.

Well there can be some “risk” depending on how you’re going about this. I’m assuming you will be wanting people outside of your home network to be able to each your server. To do so you’ll either have to open a port in your LAN firewall and expose your server on said port to the internet, or have all users who will be using this on a VPN you create.

The former being “more risky” but quantifying that risk is difficult. Ive done this in the past and don’t personally see it as a big deal. My current mumble server does not live on my LAN but I will be pulling my server out of a local data center in the nearish future and running it out of my home once more at which point a number of publicly accessible services will be hosted from my LAN.

The short answer to “can you add it to your home server” is yes. It’s not like there is some cap beyond your own system resources that prevents you from running multiple services.

He’s a spammer. Block him.

Yeah I didnt abandon Plex because I couldn’t afford it. I have a number of gripes with plex but as long as it remained free I had no strong motivated to get rid of it. Now that I would have to pay though I have no interest in keeping it around. I am quite happy with jellyfin even if it may lack polish on some of its facets and I regularly accept inconvenience to uphold my own operating philosphies.

Correct. Remote streaming used to be free. That changed…in April? I don’t remember the exact date but it was announced earlier this year and has been slowly rolling out. Now you either have to have a Plex pass for your server or each user who wants to remote stream has to pay for a remote watching subscription and show in OPs screenshot.

There are of course ways to get around this such as all your users being on a VPN so as far as Plex can see its “internal”. I suppose if you use a reverse proxy but didn’t pass X-forwarded-for headers then that may get around it as well? I never messed with it as I was looking for an excuse to dump Plex anyway. Now I’m finally jellyfin only.

Yes, however using the relay is not a prerequisite to being required to pay for a Plex subscription. That is what he is trying to say.

I can run Plex on the open internet and not use their relay at all, however if the IP of the viewer is not an interal IP on the same subnet as Plex (I assume the same subnet is required) then you’ll be greeted with the Plex paywall.

You are absolutely correct that it costs money to run a relay, but the relay has nothing to directly do with the paywall.

DC my server is at is shutting down so I have to bring everything home. Conveniently I just got hooked up with symetric 1G fiber so that’s not too much of a problem now thankfully.

Currently exploring docker swarm as a method of using one of my external VPSs to route all external traffic though it to my hardware at home on my tailnet.

Swarm isn’t required for this but figured I’d play around with it.

From what I’ve gathered in other posts regarding Plex and jellyfin, the ones that never learned how to port forward or any other alternative solution for getting external traffic to their internal server. All the complaints I’ve read here regarding jellyfin boiled down to them relying on the Plex relay to handle the traffic for them.

Apologies for the long delay. I was using just the browser via your docker image but today I’ve done some testing with the electeon app.

Wonderful that you added PTT but it’s implementation has a flaw as the Peersuite window MUST be in focus for the PTT key to be read.

As far as the video goes, I’ve definitely confirmed that there’s is some serious frame drop which I’m assuming is directly related to the bitrate in same way. I had a friend on windows use the electron app and share his screen while I watched from the electron app on Linux. I took the following recording to better demonstrate what I’m saying. The quality has gone through multiple transcodes now but that’s not really important as the framerate is what I’m referring to anyway. https://files.catbox.moe/03f5b1.mkv