xthursdayx

I'm still having this same issue with neofetch on the latest version of unRAID. The NerdPack interface shows neofetch-20200708-noarch-1.txz as downloaded but not installed, and my syslog shows "nerdpack: Installing neofetch-20200708 package..." while every other package I have installed says something like "perl-5.32.0 package up to date, checksum ok." Any ideas why it won't actually install?

I'd also love to see the shell (bash, zsh, whatever), profile (.bashrc, .zshrc, etc), and fonts be more customizable as well... I've got some scripts running that help with this, but it'd be nice if was a little more easily customizable.

Yeah, both ferdi and ferdi-server are under active development. I'm planning to begin working again on ferdi-server-docker soon, once I I finish up another project. Glad you were able to find the things you were looking for though!

Thanks for point that out @sonic6! I'll soon be active development on the server docker again, so I'll be sure to update you @ich777 if anything I change should cause breakages.

It's not a huge issues, but I was wondering if there is a way to change the plugin header background transparency? Or change the color? I searched the thread, and wasn't entirely sure I understood the posts relating to "color". Thanks for the help! Edit: don't mind me, I'm just an idiot and was trying to adjust the header background colors in the theme engine rather than in display settings.... Carry on!

Which services are you speaking about? The ferdi-server docker image (which I developed) just runs the existing release of ferdi server, so it should be up to date with any additional work that's been done on the server (I haven't been working directly on the server repo lately, so I'm not totally up to date with the developments there). There is not a Docker image for Ferdi itself, meaning the actual front-end UI program, since that is usually installed directly on the end user's machine. I suppose one could build a Docker image based on No-VNC or Guacamole in order to have Ferdi run on your server and be accessible via WebUI, but this isn't something I've worked on.

Glad to hear it!

Yep, all that clicking "yes" will do will update the link to my Roon Unraid Template .xml, it won't actually change the settings you already have in your template. But you can ignore it as well, shouldn't make any difference as the changes I made were purely organizational any way. I'll always update here if it's necessary to make any major template changes.

It seems you're reading that warning message incorrectly... in my template the "Docker Hub URL" points to steefdebruijn's image, because he maintains the image and I haven't seen any need to fork it. The warning is telling you that the TEMPLATE URL (not Docker Hub url) of your current docker container is different than that specified by the author (me). That message is just the result of me updating my docker template repo files, which then updates them in Community Apps. You can apply the fix or not, it doesn't really matter, since I didn't actually change the template itself, just the organization of my repo. That fix also doesn't have anything to do with the other issues you're experiencing. Unfortunately, I'm not still not sure what to tell you regarding the issue you're having, particularly given that things seemed to work for you after a reboot. I will say that I run emby on a non-native port while running roon on its native ports and haven't run into any issues myself.

I'm not sure why Roon would have a conflict with Emby at 1900... When I had an issue with port conflicts it was because I was using a port in the range mentioned above. To quote the another, more recent post (from last month) from the Roon forums discussing Roon's port use: ^ That post was specifically about firewall routing obviously, but is in agreement with the post from 2015 that I quoted above from Brian, Roon's CTO. It could be that the issues you're having relates to Roon's need to use multicast, but I'm not sure. Until anyone else runs into this issue it will be a bit difficult to troubleshoot. I'll be of any help that I can though.

According to the Roon community forums, Roon uses Port 9003/UDP and Ports 9100-9200/TCP. Unfortunately, I don't know of any way to change this. That's because, although you can remap the Roon Server Docker ports to different host ports, I don't know of any way to change the ports that Roon clients (on your endpoints and controller devices) use to search for a local Roon CORE. I also ran into this same issue when first starting to use Roon but just ended up having to remap other things and let Roon use its native ports.

YACReaderLibraryServer Docker Headless version of the YACReaderLibraryServer, running on a custom base image built with Ubuntu 18.04 LTS cloud image and S6 overlay. YACReader is the best comic reader and comic manager available, with support for cbr, cbz, zip, and rar comic files. YACReaderLibraryServer makes it easy to run a home comics server to serve your comics to any device running a YACReader client (including Windows, MacOS, and Linux as well the YACReader iOS app. Setup Instructions You can choose to install one of two versions of the YACReaderLibraryServer docker image, which use two different compression backends - either p7zip or unarr. These two versions are handled via the Docker repository tags "xthursdayx/yacreaderlibrary-server-docker:pzip" or "xthursdayx/yacreaderlibrary-server-docker:unarr" in your docker settings. For the best stability and general quality, it is recommended that you install YACReaderLibraryServer with unarr, which is the default installation. It should be noted, however, that as of version 1.0.1, unarr supports fewer formats than p7zip, notably RAR5. There is also some evidence that YACReaderLibraryServer compiled with p7zip may scan and create your comic library(s) faster than the version complied with unarr, so the choice is yours. In practice, any shortcomings unarr has are rarely an issue, since the vast majority of comic books use either zip or RAR4 compression, which is handled nicely by this backend, and after the initial library creation, library updates proceed smoothly with either decompression backend. If you would like to use the default unarr backend, then you do not need to add any tag to "xthursdayx/yacreaderlibrary-server-docker` since it will default to the "latest"/"unarr" tag. The docker images are also available from the GitHub container registry: ghcr.io/xthursdayx/yacreaderlibrary-server-docker Here are some examples to help you get started creating a container from this image. If you are an UNRAID user you can access my UNRAID YACReaderLibraryServer template which is available in Community Apps. Docker CLI docker run -d \ --name=YACReaderLibraryServer \ -e PUID=99 \ -e PGID=100 \ -e TZ=America/New_York \ -p 8080:8080 \ -v /path/to/config:/config \ -v /path/to/comic:/comics \ --restart unless-stopped \ xthursdayx/yacreaderlibrary-server-docker:[tag] ### docker-compose --- version: "2.1" services: yacreaderlibrary-server-docker: container_name: YACReaderLibraryServer image: xthursdayx/yacreaderlibrary-server-docker:[tag] environment: - PUID=99 - PGID=100 - TZ=America/New_York volumes: - /path/to/config:/config - /path/to/comics:/comics ports: - 8080:8080 restart: unless-stopped Parameters Container images are configured using parameters passed at runtime (such as those listed above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container. You can change the external/host port and volume mappings to suit your needs. | Parameter | Function | | :----: | --- | | `-p 8080` | HTTP access to YACReaderLibraryServer. | | `-e PUID=99` | for UserID - see below for more information. | | `-e PGID=100` | for GroupID - see below for more information. | | `-e TZ=America/New_York` | Specify a timezone to use, e.g. America/New_York. | | `-v /config` | Directory where YACReaderLibraryServer's configuration and log files will be stored. | | `-v /comics` | The directory where YACReaderLibraryServer will look for your comics. | | tag |(Optional) The docker tag will pull your chosen version YACReaderLibraryServer, the options are pzip or unarr/latest (default). | User / Group Identifiers When using volumes (-v flags) permissions issues can arise between the host OS and the container, you can avoid this by specifying the user PUID and group PGID. Ensure any mapped volume directories on your host machine are owned by the same user you specify and you will avoid any permissions issues. In this instance PUID=99 and PGID=100, to find yours using the following command: $ id <username> # Replace with your username uid=99(nobody) gid=100(users) groups=100(users) Usage Instructions To create a new YACReader comics library run the following command from the CLI on your host machine, changing `<library-name>` to whatever you want your library to be called: docker exec YACReaderLibraryServer YACReaderLibraryServer create-library <library-name> /comics To add an existing YACReader library: docker exec YACReaderLibraryServer YACReaderLibraryServer add-library <library-name> /comics To update your YACReader library (e.g. when you've added new comics): docker exec YACReaderLibraryServer YACReaderLibraryServer update-library /comics To list all existing YACReader libraries: docker exec YACReaderLibraryServer YACReaderLibraryServer list-libraries To remove a YACReader library: docker exec YACReaderLibraryServer YACReaderLibraryServer remove-library <library-name> Accessing YACReaderLibraryServer You can access your YACReaderLibraryServer by pointing your YACReader app to: `http://SERVERIP:8080` (Replace `SERVERIP` with the correct value). Please note: YACReaderLibraryServer does not have authentication installed by default, so it is not advisable to expose your server outside of your home network. If you wish to be able to access YACReaderLibraryServer from outside your local network please use a reverse ssl proxy, such as NGINX with an .htaccess file, or a locally-hosted VPN, such as OpenVPN to access your local network. If you appreciate my work please consider buying me a coffee, cheers! 😁

Yep, I’ve done it and it worked fine. I’m happy to help work out any issues should they arise in the future, but, to the best of my knowledge, internal CORE updates have been stable for a while now.

You have to update from within the Roon app running on your computer or other device. Through the app you can update both the locally running Roon software as well as the Roon CORE running in this Docker container.

No problem. The other option (though also not ideal) would be to set up an SMB share for your comics directory on your unRAID machine and then run YACReaderLibrary on your main computer with the comics directory set to that network share. You might run into problems if you accidentally start YACReader/YACReaderLibrary with the network share disconnected, but it should work otherwise.

I hate to be the bearer of bad news, but it look like the desktop version of YACReaderLibrary no longer allows you to sync with another YACReaderLiberaryServer. This used to work fine, but I hadn't checked it in a while since I use a tablet to read my comics. It looks like the dev has made it so that only iOS devices can connect to a server. I guess this makes sense in their mind, in that they are assuming that most users will keep their comics on their main computer and then run the server option of YACReaderLibrary in order to connect the YACReader iOS app with that computer. The decreased usability is a shame, but I guess the dev is putting their energy into other areas. PS, you can find more info in the user guide, but as you might expect it's geared towards iOS users: https://ios.yacreader.com/user-guide/ I've also posted in the user forms to check with the dev to see if there is a way around this. I'll report back if anything promising arises.

Happy to help! Cheers!

Yes, by default my template stores your roonserver data in your appdata folder on your cache drive. If you don't use your cache drive for your appdata folder then you can change those volume mappings to: "/mnt/user/appdata/roonserver/app" "/mnt/user/appdata/roonserver/data" Unfortunately, if your Roon CORE is already corrupt I don't believe you'll be able to backup your Roon data by copying the appdata folder and get it to work again. I think you'll have to do as @dkerlee mentioned and delete the container from the UNRAID docker page, and then manually remove the appdata folder. You can do this any number of ways, using the command @dkerlee mentioned, using a command line based visual file manager like Midnight Commander, or by using a file manager running in another docker container, like Double Commander (available via Community Apps) to manage your directories. Then you can reinstall the RoonServer container with whatever mappings you want for your appdata directory. Of course, Roon will have to build your library from scratch which is annoying, but it happens at times to the best of us.

Thanks for pointing this out K. You're not actually doing anything wrong. I think that the issue is that web browsers can't display .cbr or .cbz files. I'd never actually tried reading any comics in my browser so I didn't realize this. YACReaderLibraryServer is generally used as a server to host your comics which are then read by the YACReader application, either on your computer, or a tablet or phone. Here is the link to the software page: https://www.yacreader.com/downloads Once you download YACReader on your computer or tablet you can link it to your instance of YACReaderLibraryServer by either being on the same network and setting it up at the local address (ex. http://<UNRAID_SERVER_IP>:8082 in your case) or you could set up a reverse proxy using something like Linuxserver's SWAG image, though if you do that I'd recommend you add an HTML password to the page because there is no built in authentication with YACReaderLibraryServer. Hope that helps.

I was just wondering if there is a reason that the version of greylog that your template pulls is 3.1 rather than the latest, 4.0.6? Is it an issue to just change the repo pull tag in my own template?

I’ve never had this happened before, but I also only ever update via my MacBook. Please keep an eye on it and report back if it happens again and post any logs you have. Cheers!

Cheers, glad it worked out!

I'm getting this same error when I try to open any documents in Nextcloud using OnlyOffice DS, as well as the error " [onlyoffice] Fatal: Track without jwt" I am able to access my onlyoffice homepage via reverse proxy without any problems. Any idea what the problem might be?

@highgear I ran into a similar problem at one point when switching over from an existing install to my new one with the updated mappings, however, once I got the volume mappings correct in my template everything worked fine. I can say that all of my mapped volume permissions are nobody:users, though I'm not sure about the permissions inside the container. Honestly, starting from scratch with the new mappings is probably the simplest thing to do, though I know you may want to avoid that if you have a lot of user-added information. You can try to back up and and then install from my template and then restore, but @mikela indicated that that didn't work for them here:

Great, thanks!