allanp81

I would just like to be able to ssh from this docker to another device on my network.

What are the better ways you can think of?

I don't need the server, just the client. I can SSH into the container by enabling tailscale SSH but can't SSH out of the container to my other physical device running pihole.

Any chance of getting ssh client added to this docker? I wanted to try and set 2 pihole instances with HA scripts but this isn't possible if I can't SSH out of the docker container to the other pihole instance.

How are you going to format the new drives and what OS will you run before you move the USB drive over?

Is that the docker log or the kodi.log?

What does the kodi.log show?

Check that the "flash\config\shares" match the names you see in the Unraid console. I had a share named "P" that refused to move and when I looked at the P.cfg in that path it was called p.cfg and was skipping it. As soon I can changed the case on the p.cfg to P.cfg it fixed the issue. It was fine prior to 7.x so something changed in how the mover checks for work to do.

The open source driver worked within jellyfin but not Emby. I have rebooted after selecting a different driver to test. I have switched back to the production driver and will try Emby again but I suspect it'll still not work. It seems that it's an Emby issue though and nothing to do with the nvidia driver so I'll go back to Emby. I paid for it so I will try and get some support from them...

I've been trying all of the driver versions offered to me, none work but I've just done some testing with Jellyfin this afternoon and HW transcoding appears to be working fine so this looks like it's unique to Emby for some reason.

server-diagnostics-20250305-1145.zip

Anyone having issues with Emby server and transcoding? This used to work perfectly for me but now it just fails to start any video stream if transcoding is required. The FFMPEG log that Emby generates shows it selecting the Nvidia card etc. but then just fails seemingly with no actual error. I've tried the official Emby dockers and also the linuxserver versions and both fail the same way. I can see from the nvidia-smi output that ffmpeg at least attemps to start transcoding 3-4 times and then fails.

Thanks so much! This thread helped me solved my problem with the mover not working as well. 1 of my shares is simply named "P" in uppercase but the share config file was named "p.cfg". I renamed this file on my flash to "P.cfg" and that solved the problem.

Nope, never have.

I'm seeing exactly the same problem and can't work out why at all. I have some shares that are being moved successfully and some that aren't with no obvious differences between them. Was working fine prior to the 7.x upgrade.

Has anyone managed to get nextloud working with swag using a subfolder instead of subdomain? ie. my.domain.com/nextcloud? I used to use this with this docker back in the day and it worked perfectly but with the change a year of 2 ago I've never been able to get it working.

Has anyone managed to get this working via swag as a subfolder rather than subdomain? It used to work fine but since the changes last year I just cannot get it to work anymore and I've followed the guides on here and on the nextcloud docs as best I can.

Yes, within the motioneye appdata directory you'll see some files named "thread-1.conf", "thread-2.conf" etc. that relate to each camera. In theory stop the docker, identify which config file applies to which camera, make a backup of the file then change the necessary properties in the file and restart the docker.

Has anyone managed to get this working as subfolder yet? ie. https://myserver/nextcloud?

Has anyone managed to get this working as a subfolder instead of the default? I've gone through the nextcloud documentation but it doesn't seem to work. If I do the changes in the config.php to add /nextcloud so http://192.168.x.x:8443/nextcloud instead of just http://192.168.x.x:8443/ it doesn't work so means I can't get it work via reverse proxy either.

Under settings and then Media Management (make sure you enable show advanced) there's a section if you scroll down so that you can set permissions.

I think my problem with trying to get this working again via reverse proxy is that I can't get it to work even internally with a changed webroot. If I set this on the config.php: 'overwritewebroot' => '/nextcloud' It doesn't work for some reason. I can't see any obvious errors in the error.log or even anything really in the access.log that would suggest why it fails once the webroot is changed.

Nope, I've tried everything and have given up with trying to get it working externally again. Worked perfectly previously but I've spent hours and days trying to get it working again.

It seems something might've changed, I used to use the /nextcloud webroot but since the docker was updated I can't get it working anymore. I've tried replicating all of the settings I had before with swag and nextcloud but it just refuses to work.

Originally I tried to get my docker to update etc. but gave up and ended up renaming the appdata folder and letting it create new and then copied back my config.php. My instance works fine internally and things sync etc. but I can't get external access to work anymore when I try to replicate the settings I had applied to nginx and nextcloud. The main issue from the logs appears to be an SSL handshake problem but I don't recall having to do anything fancy other than change the url base to /nextcloud and add ips and hostnames to the trusted domains and trusted proxies etc.