I'm having a weird problem... I created sonarr radarr etc LXC containers... all of them work perfect and then few days after running it is impossible for me to use the WebUI anymore and I have to destroy the container and create it again and also do the settings again.

It is weird because I use "ip a" command and I can see their ip's... I can ping them from another computer and I can see they are running correctly... It is just that the WebUI doesnt work anymore. Maybe the port changes? I tried to use static ip as well and nothing... when a container gets unreachable I cannot find the way to reach it again. Anybody knows what can be happening?

​

I'm having a weird problem... I created sonarr radarr etc LXC containers... all of them work perfect and then few days after running it is impossible for me to use the WebUI anymore and I have to destroy the container and create it again and also do the settings again.

It is weird because I use "ip a" command and I can see their ip's... I can ping them from another computer and I can see they are running correctly... It is just that the WebUI doesnt work anymore. Maybe the port changes? I tried to use static ip as well and nothing... when a container gets unreachable I cannot find the way to reach it again. Anybody knows what can be happening?

​

I created a shared directory specifically to share data between my LXC's. The directory can be accessed from any LXC and I can create subfolders in it. But any LXC can access the subfolders or files created by another LXC in that directory (which was the only purpose of this).

What is going on? I was using the webUI to create the directory and my LXC's are privileged. Do I need to mount something or I missed a step somewhere?

I have a media server based on Ubuntu server 22.03LTS with Kernel updated to the latest stable 6.5.7 running on Proxmox 8 as a VM. My machine is a Beelink EQ12 with an intel N100. Im using Jellyfin server 10.8.

My obstacle is that I cannot activate the transcoding on Jellyfin because I cannot see the renderD128 in /dev/dri. I thought It was because my processor is quite new so I needed the latest kernel but.. after installing the latest kernel and rebooting... I still don't see the renderD128.

It's frustrating. I don't know what else to do.