Man I love TUIs, Great work!

Hospice is end of life care.

I had to look it up since I’m not a native English speaker.Truly a sad day for selfhosters, his scripts have helped the community tremendously, I hope the best for him and his family.

Thanks for the nice write-up, saving it in case I find myself behind CGNAT in the future.

I’m not sure I understand what you are trying to do, since you’re gonna have a vps, why not move your reverse proxy over to it and have that as the only entrypoint to your network using tailscale or wireguard for it to connect to your home services?

Seems they’re running a podcast now:

https://youtu.be/xMTK3aaBOz4

On for me in the EU

The decision is a setback for the Commission, which fined Google €8 billion in three competition cases. Just last week, €2.42 billion was confirmed as a final decision.

Google appealed the fine in June 2019, arguing its practices were designed to ensure a consistent user experience. The European Commission now has two months and 10 days to appeal the decision to the European Court of Justice (ECJ).

So, it’s just a small part of the fine they got, let’s see what happens with the appeal.

For android TV you should use smarttubenext, same as tubular, but with a tv interface.

I have a couple of nodes we take on our hiking trips for emergencies or when we split up and it works pretty well. It has a surprisingly good range with the right antennas.

This one is a single flatpak that is self contained, the other one is a script that downloads the emulators one by one, in both cases you can pick and choose which ones you want to download from a list and they’ll do the rest if you provide the ROMs

I’ve been using their 1€/month vps for a couple of years now as a reverse proxy, but I use HAproxy and wireguard. It’s been working flawlessly.

Updated to this version, but it’s still not working for me.

I sometimes connect my steam deck to a computer screen with keyboard and mouse to play, yes.

I played it while connected to my screen, I seem to recall that in desktop mode, friends window, right click a friend and start steam play together, all while the the game is running.

I’ve played shredders revenge on my deck with 4 players via remote play together and had no issues whatsoever.

Each player was using he’s own controller to play. What was your problem exactly?

You have to use the Remote play together interface to map the player controllers to the local controllers 1 through 4, but that’s it.

Now they’re working

They’re not working for me

Might be some NFS permissions problem, can you try some other temp directory with say 777 permissions to see if it’s that?

Ah! now I see the problem

permission denied, mkdir ‘upload/library’

It’s clearly having permission problems with the image library directory.

Also:

volumes:
 - /mnt/NAS-immich-folder:/mnt/immich
 - ${UPLOAD_LOCATION}:/mnt/immich

with this command you are trying to mount this directory from your LXC machine:

/mnt/NAS-immich-folder

into this directory inside the immich container:

/mnt/immich

And then you also try to mount a second directory there in the next line. But immich doesn’t use /mnt/immich for its library, it uses this:

/usr/src/app/upload

You should NOT edit the default docker-compose.yml file. Instead you should only edit the .env file like so:

UPLOAD_LOCATION=/mnt/NAS-immich-folder

I can also see that there’s a specific tutorial on how to set it up with portainer. In that case you might have to edit the docker compose file to replace .env with stack.env and place the contents of the env file in the advanced-> environment variables of portainer.

Try these things and ask here again if you can’t get it running.

That all seems correct, the way to expose services with a docker-compose is by using the:

ports:
  - 2283:3001

That means that you expose whatever is at port 3001 in the cointainer (in this case the Immich server inside the docker container, which is exposed by default to 3001) to port 2283 of the host machine (in this case, your LXC container). So it should work if everything else is set up correctly.

The 172.x.x.x networks are normal internal networks for docker to use, normally you needn’t care about them because you just expose whichever port you need via the ports command above.

Are you following this step by step to set it all up? is your .env file properly set up? did you check the containers logs?