-
Posts
397 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by xthursdayx
-
-
58 minutes ago, Joshndroid said:
After some further looking it depended on the client running on the system... So once i started checking out the nightly client ferdi releases I could see more services listed (such as nextcloud calendar)
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!
-
1
-
-
-
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!
-
On 6/11/2021 at 2:17 AM, Joshndroid said:
Managed to get this up and working this afternoon; sqlite, ssl, reverse proxy, custom domain, smtp, all working a treat.
I had checked ferdi out, rebuffing yet another service with a bunch of my data, prior to finding your container for the backend stuff.
Love it.
Thanks for the work and keep the updates coming
one thing I do see is that the services offered are not as plentiful as those in their github or on their 'services' page
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.
-
19 hours ago, xrqp said:
I clicked "fix" and it fixed it. Easy peasy. Now my "fix common problems" is clean, which I like. Thanks.
Glad to hear it!
-
13 hours ago, xrqp said:
Roon and Emby seem to be working now. Maybe it just needed one or two reboots.
xthursdayx, do you mean that the TEMPLATE URL warning is to be expected, but of no concern, and that it is OK, regardless if i click nothing, click fix, or click ignore? If the answer is "yes" that would be good news.
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.
-
51 minutes ago, xrqp said:
10 minutes later. With emby kept 1900 to 1900, I rebooted unraid. Both roon and emby containers autostarted. Emby works correct - I can delete files. But now I get a "fix common problems" message that says
Before clicking "apply fix" i look at roon container settings and it says "Docker Hub URL: https://hub.docker.com/r/steefdebruijn/docker-roonserver/ " Is this bad? Is it a result of UPNP not working? Should I click "apply fix"?
Next, I turned off all autostarts then rebooted again, started only roon, kept emby off, and I still get the same warning about roonserver template URL.
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.
-
7 hours ago, xrqp said:
So you figured out that same port was being used for roon container and other container? How?
The way I did it: looking at error logs when trying to start emby said somethin like "conflict with port 1900". Roon did not say what it used, so I stopped Roon container. Only then was I able to start emby. Then I remapped emby 1900 to 1901. Then both could run.
Maybe someone here can figure out how to see what ports it uses.
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:
QuoteNot official support but, the Roon core must be reachable not just via UDP 9003 and TCP 9100 - 9200 ports, but multicast and broadcast communication must also be allowed in the firewall.
^ 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.
QuoteBrian LuczkiewiczRoon Labs: CTO
May '15
Reiterating it here in case anyone else has similar needs in the future:
Starting in the next build, you’ll want to forward:
UDP port 9003
TCP ports 9100-9200
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.
-
9 hours ago, xrqp said:
What ports does this container use? Can I somehow see which ports it uses, like with most containers?
I had a conflict, where an Emby container wanted to use port 1900. Some trial and error gave me a clue that this Roon container may have used 1900. I reassigned emby port 1900 to 1901, so now emby runs, but not well. I have had problems with emby, and other unraid things, so now I wonder if this was the cause.
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-stoppedParameters
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! 😁
-
1 hour ago, xrqp said:
Did anybody do the Roon update that came in about May 20? I am afraid to be the first. Every time I start the program it nags me.
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.
-
On 5/16/2021 at 5:04 PM, dan4UR said:
Quiet happy with this docker. Runs well. But if there'll be an update, would the docker container also be updated or does the core get the update automatically ?
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.
-
11 hours ago, Keek Uras said:
Well, isn't that something. I did take a look at the user guide before posting but didn't find the answer there and this explains why.
I used to use YACR with it installed to my local box and my comics on another internal drive but migrated them to my unRAID server, with the thought of it becoming my complete media solution. Worst case, I go back to using Ubooquity for my comics. It's not the worst but can be a little finicky. I appreciate the response. Thanks for looking into it!
~K
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.
-
22 hours ago, Keek Uras said:
Ok, sorry, apparently one more question - how do you format the URL to make it work? I've tried the IP + port with and without http:// and nothing loads. The webpage loads fine in a browser. Here is what I have now:
I tried it after adding /library to the path and got no love there either. Any ideas?
Thanks,
~KI 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.
-
1
-
-
9 hours ago, Keek Uras said:
Thank you for the response. I apologize that I had assumed incorrectly
I installed it and automatically expected it to work more like Calibre Web. No problem at all, I'll install the reader on my PC since it's just for me anyway. Thanks again!
Happy to help! Cheers!
-
7 hours ago, ridley said:
I have a feeling that the data was being stored on the Cache drive and my issues have been caused by the cache drive dying.
Am I right in thinking that the data was being stored on the cache drive is what is indicated
"/mnt/cache/appdata/roonserver/app",
"/mnt/cache/appdata/roonserver/data"
what this indicates or am I barking up the wrong tree?
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.
-
1
-
-
32 minutes ago, Keek Uras said:
Hello! I've set up yacserver and created the library but when I click on the read link, I just get a text output.
Any thoughts on what I might have done wrong? Thanks in advance!
~K
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.
-
1
-
-
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?
-
6 hours ago, xrqp said:
A few post above this I reported my Roon core update went well. One possible minor glitch is that it may require a restart, or a power cycle, especially if you also update a remote later. Here is why I say that:
The Unraid core update was working good for me for a few days, then came an update on my remote ipad. Then it worked for an hour. Then it stopped working. I tried power cycle on my Auralic G2 (a music computer between Unraid and DAC), which usually fixes these issues, and I tried other things for 40 minutes, with no success. Then when I did power cycle on Unraid, I was able to get things to work again.
Prior to this I never needed to restart Roon docker or power cycle the Unraid NAS to fix problems. But next time it won't take me 40 minutes before I try that. Has anyone else had this happen?
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!
-
10 hours ago, highgear said:
Thanks for your work on this docker, looking forward to no update issues in the future!
Cheers, glad it worked out!
-
On 2/14/2021 at 4:24 PM, xthursdayx said:
I'm getting the following error in my Nextcloud log when trying to open documents via the Nextcloud mobile app on iOS:
Fatal: Download without jwtFatal: Download without jwtAnyone know what might be causing this problem?
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:
-
On 4/10/2021 at 10:59 AM, gustomucho said:
@xthursdayx It is actually much easier than that. Simply copy the contents of your "/mnt/user/appdata/rutorrent/rtorrent/rtorrent_sess" into the following folder : "/mnt/user/appdata/binhex-rtorrentvpn/rtorrent/session"
Everything should be good to go.
Great, thanks!
-
5 minutes ago, binhex said:
this is why:-
so it will recursively be setting permissions on /mnt/user, which will obviously take some time!, edit this path and change it to a more specific folder, /data is used to store downloaded data, so something like /mnt/cache/appdata/downloads/ would be a better fit and should get things running for you.
Ah okay, I just assumed this was used to map volume access, I didn't realize it was specifically the download directory. Thanks!
I installed it and automatically expected it to work more like Calibre Web. No problem at all, I'll install the reader on my PC since it's just for me anyway. Thanks again!
Web Console color profiles (accessibility issue)
in Feature Requests
Posted
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.