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.