smikwily

Confirming that COUCHDB_USER / COUCHDB_PASSWORD are needed and once added, it works. I was confused when I saw a v1 and a v2, especially when v1 was listed as official and had the official tag in Community Applications. Then I noticed that @spants makes both of them and figured v2 must be a new version of the template vs the version number of the actual software itself.

Thanks for this. I was trying to recover backups, etc. and wasn't have much luck. Checked here to see if I was missing anything and after restoring my original files and nuking the logs.db, it started working without issue!

Requesting: Affine Website: https://affine.pro/ Docs: https://docs.affine.pro/affine/starting-point/install-affine/docker Docker: ghcr.io/toeverything/affine:nightly-latest

I've added a variable for this and I'm still getting the exact same error. Update: I just nuked it. Started over and it seems happy now. Surprised the app template doesn't have the new variable by default.

If you are looking to shuck an external drive from an enclosure, make sure you check the prices on https://shucks.top/ to see if it is a decent price.

Not sure about them, but changing that to remove the http:// and the port helped me get it working. Thanks!

Same for me as well. Thought it was just dragging between screens that was causing it, but also seeing it when resizing.

Just checking back in to let you know that everything has been running a lot smoother the last two weeks with no lockups. I think I figured it out by accident. I had opened things up to remove some hardware to see if that could be causing some problems and decided to move my USB drive to an internal USB port that was on my motherboard. While doing that, I noticed that I had apparently plugged both sets of 4 pin USB cables for my front ports into the same 9 pin header. I wondered if that could be causing the problem, so I pulled the cables out. Both of them were looking just slightly "melty", so I just removed them, as I wasn't using the front ports anyhow. That alone seems to have helped with the random left field lockups. Thanks again for all your help and suggestions!

Ok. I was working on things off and on this AM after getting this set up. Just noticed my server was down. Nothing is jumping out at me here, but including everything from when it started until some of the early parts of the powering it back up via hardware reset: Aug 23 11:19:52 SMIK-TOWER rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="21279" x-info="https://www.rsyslog.com"] start Aug 23 13:44:14 SMIK-TOWER kernel: br0: port 2(vnet0) entered blocking state Aug 23 13:44:14 SMIK-TOWER kernel: br0: port 2(vnet0) entered disabled state Aug 23 13:44:14 SMIK-TOWER kernel: device vnet0 entered promiscuous mode Aug 23 13:44:14 SMIK-TOWER kernel: br0: port 2(vnet0) entered blocking state Aug 23 13:44:14 SMIK-TOWER kernel: br0: port 2(vnet0) entered forwarding state Aug 23 13:44:18 SMIK-TOWER kernel: usb 2-1.2: reset high-speed USB device number 4 using ehci-pci Aug 23 14:13:53 SMIK-TOWER kernel: usb 2-1.2: reset high-speed USB device number 4 using ehci-pci Aug 23 14:13:56 SMIK-TOWER kernel: usb 2-1.2: reset high-speed USB device number 4 using ehci-pci Aug 23 14:43:40 SMIK-TOWER kernel: perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 Aug 23 17:58:54 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Aug 23 17:58:54 SMIK-TOWER rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Aug 23 17:58:54 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): br-cc709da2b6c7: link is not ready Aug 23 17:58:54 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): hassio: link is not ready Aug 23 17:58:54 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): br-538e29e4d2f7: link is not ready Aug 23 17:59:43 SMIK-TOWER kernel: docker0: port 1(veth8c6e751) entered blocking state Aug 23 17:59:43 SMIK-TOWER kernel: docker0: port 1(veth8c6e751) entered disabled state Aug 23 17:59:43 SMIK-TOWER kernel: device veth8c6e751 entered promiscuous mode Aug 23 17:59:43 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): veth8c6e751: link is not ready Aug 23 17:59:45 SMIK-TOWER kernel: eth0: renamed from veth76fd770 Aug 23 17:59:45 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8c6e751: link becomes ready Aug 23 17:59:45 SMIK-TOWER kernel: docker0: port 1(veth8c6e751) entered blocking state Aug 23 17:59:45 SMIK-TOWER kernel: docker0: port 1(veth8c6e751) entered forwarding state Aug 23 17:59:45 SMIK-TOWER kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Aug 23 17:59:49 SMIK-TOWER emhttpd: shcmd (106): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Aug 23 17:59:49 SMIK-TOWER kernel: BTRFS: device fsid 0721a6b0-6d5d-400e-86e2-ee1afdfcc283 devid 1 transid 104 /dev/loop3 Aug 23 17:59:49 SMIK-TOWER kernel: BTRFS info (device loop3): disk space caching is enabled Aug 23 17:59:49 SMIK-TOWER kernel: BTRFS info (device loop3): has skinny extents Aug 23 17:59:49 SMIK-TOWER root: Resize '/etc/libvirt' of 'max' Aug 23 17:59:49 SMIK-TOWER kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 Aug 23 17:59:49 SMIK-TOWER emhttpd: shcmd (108): /etc/rc.d/rc.libvirt start Aug 23 17:59:49 SMIK-TOWER root: Starting virtlockd... Aug 23 17:59:49 SMIK-TOWER root: Starting virtlogd...

Thanks. Just configured this.

Diags attached if that will help. Again - this is when things are running. When it locks up, I can't get to anything without a hard reboot. smik-tower-diagnostics-20200823-0033.zip

I thought originally I had some bad memory, but then figured out that I had it installed incorrectly. Everything seemed to be working better, but over the last few days, I've had a few random lockups. I can't get anything to respond at that point. I can't get to the browser based GUI, can't SSH, and even with a local monitor, nothing will respond. Any suggestions on where to start? I just did a diagnostics run, but I don't think that is going to do any good now after having to reboot to get it. X9DRH-iTF w/ 2x Intel Xeon E5-2650V2 2 sets of 2 sticks each 32GB Samsung memory: M386B4G70DM0-YK0 (128 total) F80 for cache 500GB Unassigned for Plex Caches 2 Parity Drives 32TB Total Storage I bumped the warning and danger levels up on the F80, as it runs hot and Unraid complains about it from time to time. I found the usual running temps and adjusted them up a touch higher than I had them previously.

So, I've been thinking of running ArchiveBox for archiving some stuff for reference. There is an Unraid docker available, but I'm not a huge fan of having to stop the docker, change the argument, then start it up and guess as to when it has finished with the requested site. Today I decided to give it another go since they announced their 4.9 update. After some fiddling around with it and doing some research, I was able to get the server to run and stay running by putting "server 0.0.0.0:8000" in the Post Arguments box. That allows me to get to the site and see the GUI, but if you try to click on the Admin or Add Link links, it brings you to a login page. Per that page (and their docs), you are supposed to be able to add a user by running the following from the shell: archivebox manage createsuperuser But when I did that, it threw the following error: [!] ArchiveBox should never be run as root! It also linked to this page: https://github.com/pirate/ArchiveBox/wiki/Security-Overview#do-not-run-as-root Now, per that page, I added the ALLOW_ROOT=True variable and also tried the config file, but it wasn't working, so I decided to try their Github issues page: https://github.com/pirate/ArchiveBox/issues/395 I found out from there that apparently the ALLOW_ROOT had been removed from the program (but not from the docs yet) and they asked about running it as another user. I added a user per the devs recommendation and it either did it or had already done it, as it said the user existed. But when I tried to run it by using "-u archivebox" or even trying to change the permissions, it would error out or revert when I changed the configuration of the docker. So, does anyone have any suggestions or is it possible to run the docker as another user? (And feel free to correct me on the incorrect usage of docker vs container, as I don't quite have that correct in my head either TIA!

Any plans to add ffsubsync? https://github.com/morpheus65535/bazarr/wiki/Installation-Docker#hotiobazarr

Very minor issue, but I'm trying to get Miniflux up and running, but was having some issues, so I clicked through to your GitHub docs. In the link section, you have the Docker Hub and Github links swapped under Miniflux and Moodle. I was able to see it to get the right place, but thought I'd let you know. Since I'm posting, I'll ask - does the postgres:// link support ports? I'm having a heck of a time getting the authentication for Postgres working, but will admin I'm still learning my way around it and pgAdmin. Edit: I got the port to work. Not sure if the special characters in my password were causing issues or what, but I ended up nuking the user and database in Postgres and creating it again using no special characters in the password and it currently seems happier.

Ok. Thanks. That makes sense for both this question and other similar questions I've had. Is there a reason that the only file/folders in Cache at all is /mnt/cache/system/docker/docker.img ? Is that because it is the only thing left on Cache? Edit: It is throwing me because my used space on my cache drive is pretty much twice what that single file size is. So, as if it is in two locations. As stated, I have Docker turned off and have switched all shares to Cache: Yes.

Should I have a docker.img file in both /cache and /user? I think I've made a few 'changes' in my system over the last few weeks which caused some duplication of files and I've gotten most of that taken care of using the "turn off docker and set appdata to Prefer/invoke Mover" to get appdata more or less moved to where it should be, followed by setting everything to cache/invoke Mover. As it stands, I have one file left in in /cache and it is /system/docker/docker.img and I'm not sure if I should nuke it. TIA!

Saw the update and the fixes. Confirmed all three working. Thank you!

Not sure if it was moved or merged, but the link to the UD thread seems to be different than linked above. Since I was doing some searching on the above and kept ending up here and clicking on the broken link, I figured I'd leave a working one here: https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/

Just found this tonight and bought it. Noticed a few minor things. - I set my temp units to Freedom, but the disk temps are still in Correct. - I rotated my phone to see if I could see some more detail on the Disks tab, but when I did, the page flipped to Dashboard, but Disks was listed as the active tab. It flips back to Dashboard on portrait to landscape no matter what tab you were originally on. - When I rotated and then selected the Disks tab (to get around the above), the top "graph" section of the page won't scroll with the full page, acting like a static-ish header. That leaves a very skinny scrollable area to view and you have to find that area in order to scroll. Love what you have so far! Sent from my VS996 using Tapatalk

Thanks for this as well. I was having issues getting this version up and running and was wondering if there was another way to do this. Found this thread and am happy to see an update/rework is coming!

https://hub.docker.com/r/shaarli/shaarli/dockerfile VOLUME /var/www/shaarli/cache VOLUME /var/www/shaarli/data EXPOSE 80 I learned about Expose, when I was trying to get it up and running. Is Volume what I need to work with for data locations? This is their docker-compose.yml on Github, but I'm using the docker.com docker (if that makes sense and is a thing...)

Hi. Still learning my way around Unraid and the forums, so sorry if this is in the wrong place. TIA. I haven't started dumping a lot of stuff into Unraid yet, as I'm afraid I'm going to screw something up and lose data/info. I've spun quite a few things up and go them working, but nothing I couldn't live without. Today I started trying to figure out why my Docker memory usage was up to 82% of my available 15.7GiB. After trying a few suggestions, I saw reference to the fact that you can just spin down Docker, nuke your docker.img file, then re-add the apps from Apps > Previous Apps. I did that and noticed that all the Dockers were up and running, but I couldn't access them. Then I noticed that the my user defined network was gone. I found a SI1 video that I used when I was first setting things up and found how to recreate that, which I did. I went into all of my dockers and noticed they were all set to the user defined network, but none of them seemed to be using it. I switched all of their Network Types to something else, then switched them back to the Custom network, then hit Apply. They would stop and start over again, then they would work. I manually did that for everything and thought that everything was fine. But I noticed that some of the more dockers that I a little more problem with weren't working. And when I got logged in, they acted like they didn't know my users or have any data. So, I'm OK if I lost some data. Again - I haven't jumped in because I want to know what my limitations are and how to work around them. But, if that data is gone, how can I avoid that in the future? From what I can tell, APPDATA is a configuration in most of the CA options and are usually set by default (but can be changed), but that setting doesn't seem to be readily available in everything. Example: shaarli - it took me a little while to figure out to make the custom port to get that up and running in Unraid, but now the port is there, but the data is gone. After checking the shaarli docs, it refers to data_dir in their config, which seems to point to "data". Similar with trilium: TRILIUM_DATA_DIR=/data https://shaarli.readthedocs.io/en/master/Shaarli-configuration/#configuration-file-example > Under resources > "data_dir": "data", Do I modify that config file to point it where I want it to go or do I make a "path" or other docker level change to point that where I want the data stored, so that data isn't lost if I do similar (or worse) in the past. I want to get over to doing backups and such in the near future, but I'm not there yet tl;dr - Docker using too many resources. Nuked and recreated docker.img. Reinstalled apps from CA, but a few lost data. Trying to figure out how to "redirect" the data config on a few dockers - ex: shaarli, trilium - so that doesn't happen again. Thinking that may have contributed to original docker.img issue?

Does anyone know if it is possible to "expand" a podcast that was previously added? I added a podcast and had most of them downloaded before I realized that it was limited to 200. I changed the program default to 500, but the original won't update past 200.

I feel like an idiot, but after having issues with SMB shares not connecting properly after reboots or upgrades and removing a SMB share and not being able to get the first "Next" button to click, I feel like I need to ask for some pity for those that can't read good. The "Choose Protocol" is right there with pictures, but for some reason, my brain thought it was going to ask me that on the next page. Both icons are grayed out and the Next button appears to be clickable even when nothing is selected, but the Next button doesn't actually work. After disabling skins, rebooting, rolling back, upgrading again, uninstalling and reinstalling plugins, I have to ask - can you make it slightly less idiot proof? It wasn't until I noticed the cursor change on mousing over the Windows icon that I realized what I needed to do on that prompt... TIA!