
allanp81
Members-
Content Count
291 -
Joined
-
Last visited
Community Reputation
7 NeutralAbout allanp81
-
Rank
Member
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
[Support] Linuxserver.io - TVHeadend
allanp81 replied to linuxserver.io's topic in Docker Containers
if you terminal into the docker and list devices is it definitely being passed through? I think lspci might show it (unless someone else knows the answer). -
I've done it, it's fairly straight forward to migrate the DB from mysql to mariadb, you can use mysqldump to backup from mysql and then import into mariadb. It's slightly more complicated to edit the nextcloud config though if you're using different DB credentials. In theory if the credentials are the same then nextcloud will just work when you restart the docker.
-
[Support] Linuxserver.io - Kodi-Headless
allanp81 replied to linuxserver.io's topic in Docker Containers
Yes I have to agree with others, I'm not really sure what you're trying to achieve. If you just want a simple way of browsing your collection then Emby or Jellyfish is a much easier (and nicer) way to do this. Whatever you use though will be "out of sync" with your clients if the clients have their own local libraries. -
[Support] Linuxserver.io - Kodi-Headless
allanp81 replied to linuxserver.io's topic in Docker Containers
Well then in theory it'll work "standalone", don't see why not and then you can just browse via the web interface but if you have another client they'll show different results the next time you do a library scan on either. It's fairly easy to set up an SQL docker and then use a shared library. -
[Support] Linuxserver.io - Kodi-Headless
allanp81 replied to linuxserver.io's topic in Docker Containers
You need to use an SQL database to store your library otherwise I don't see why you would want to use this? You can configure all of your sources on another kodi instance and then copy the sources.xml over to the docker container for the kodi headless. -
[Support] Linuxserver.io - Kodi-Headless
allanp81 replied to linuxserver.io's topic in Docker Containers
I use it with others that can use the API to kick off library scans. It works great. You can set up scripts yourself to do this if you want as it's fairly easy to use the API to do certain functions. -
allanp81 started following Idiots Guide to running a python script and Current Pending Sector Count warnings on SSD
-
Current Pending Sector Count warnings on SSD
allanp81 replied to Gizmotoy's topic in General Support
I've just got 1 of these drives and can confirm it's still an issue. I'm mounting via the unassigned devices plugin as well. -
[Support] Linuxserver.io - TVHeadend
allanp81 replied to linuxserver.io's topic in Docker Containers
I asked that before and was told there was no specific to use 1 over the other. I went for the docker route as I thought it was just easier to see how you're setting up directories for recordings etc. when using the docker interface. I think you still need the DVB plugin and then pass the device through to the docker. I use a networked HD Homerun so it just worked. -
Get the User Scripts plugin, that will allow you to set any schedule you like.
-
I've got an N2 as well, great bit of kit and plays everything I've tried on it including near 100Gb UHD remuxes.
-
Large copy/write on btrfs cache pool locking up server temporarily
allanp81 replied to aptalca's topic in General Support
Sorry I'm only running beta on my backup server currently which has no cache drives. -
Large copy/write on btrfs cache pool locking up server temporarily
allanp81 replied to aptalca's topic in General Support
It's so annoying, I had to re-architect my server to get around this problem (and obviously there was expense involved),. -
[Support] Linuxserver.io - Nextcloud
allanp81 replied to linuxserver.io's topic in Docker Containers
*EDIT* I think I answered my own question, seems to be a let's encrypt issue. My nextcloud instance seems to have stopped working this morning for no obvious reason. The nginx log is showing the following that it wasn't showing before: 2020/06/30 09:31:14 [error] 370#370: *355 directory index of "/config/www/" is forbidden, client: 192.168.7.28, server: _, request: "GET / HTTP/1.1", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.7.28, serv