bigbangus

I get a warning from within duplicati GUI when I configure a backup to run-script-after. After clicking on the warning the log reports success and no details on what went wrong. The script itself works, but I suppose it never reaches "exit 0"? Any help is appreciated. MESSAGE="$DUPLICATI__OPERATIONNAME $DUPLICATI__PARSED_RESULT" TITLE="$DUPLICATI__backup_name" APP_TOKEN="hidden" USER_TOKEN="hidden" curl 'https://api.pushover.net/1/messages.json' -X POST -d "token=$APP_TOKEN&user=$USER_TOKEN&message=\"$MESSAGE\"&title=\"$TITLE\"" exit 0

Gotcha yeah that makes no sense it would work with the image version.

What’s the container log say? Sent from my iPhone using Tapatalk

Add a container variable 'PAPERLESS_OCR_ALWAYS' and set to 'true'. See the original post section 3.2 how to customize paperless.

Whenever I scan a bunch of papers into a large PDF document, paperless always skips OCR. Any thoughts? Consuming /consume/Scan1232131.pdf ** Processing: /tmp/paperless/paperless-8qv7_pge/convert.png 494x643 pixels, 3x16 bits/pixel, RGB Input IDAT size = 70480 bytes Input file size = 70561 bytes Trying: zc = 9 zm = 9 zs = 0 f = 0 IDAT size = 52581 zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 52451 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 52451 Output file: /tmp/paperless/paperless-8qv7_pge/optipng.png Output IDAT size = 52451 bytes (18029 bytes decrease) Output file size = 52508 bytes (18053 bytes = 25.58% decrease) Skipping OCR, using Text from PDF Unable to detect date for document d Document 20200903202020: Scan1232131 consumption finished paperless-consumer root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='paperless-consumer' --net='proxynet' --cpuset-cpus='1,3,4,5,13,15,16,17' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PAPERLESS_OCR_LANGUAGE'='eng' -e 'PAPERLESS_OCR_LANGUAGES'='eng' -e 'PAPERLESS_FORGIVING_OCR'='true' -e 'PAPERLESS_INLINE_DOC'='true' -e 'PAPERLESS_FILENAME_FORMAT'='{added}_{title}_{created}' -e 'USERMAP_UID'='99' -e 'USERMAP_GID'='100' -p '8001:8000/tcp' -v '/mnt/user/appdata/paperless/data':'/usr/src/paperless/data':'rw' -v '/mnt/user/paperless/Media/':'/usr/src/paperless/media':'rw' -v '/mnt/user/paperless/Consume/':'/consume':'rw' -v '/mnt/user/paperless/Export/':'/export':'rw' 'thepaperlessproject/paperless' document_consumer

Is it AMD Starship/Matisse Audio Controller?

Ooo what's that? Any literature I can read to understand what that means for my unraid server?

Yeah @rachid596 got me setup with a custom build too. Super helpful and then I learned to make my own thanks to @ich777 's helper container. FYI the issue is fixed in kernel 5.7.5 and after for AMD audio and USB passthrough. So Unraid 6.9beta24 and after will have this fix.

For reference I was able to set the password in letsencrypt by opening a console window on the container: htpasswd -c /config/nginx/.htpasswd <user> New password: ********* Re-type new password: ********* Adding password for user <user> Thanks again for the help. I guess it's up to me to choose between the container auth or the nginx auth.

Got it working by using 'binhex-delugevpn' in the sonar.subdomain.conf. Thanks again. Now just a question of security like you said... location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app binhex-delugevpn; set $upstream_port 8989; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location ~ (/sonarr)?/api { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app binhex-delugevpn; set $upstream_port 8989; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }

So the security built into the sonarr docker GUI isn't sufficient?

OK I see now they are listed in the docker tab while the container is running. Are these static or will they change as I add/remove containers over time?

How do you determine the IP of the container? Is it something you have to set statically? Here is my sonar config. it's network is passing through binhex-delugevpn in extra parameters.

Could you post an anonymous sample.conf. I'm fairly new to the game.

I've got binhex-sonarr,binhex-radarr,binhex-sabnzbget all using the container network of binhex-delugevpn for vpn with the argument "--net=container:binhex-delugevpn". I've got nextcloud,OnlyOfficeDocumentServer,tautulli,binhex-plex running through a reverse proxy using letsencrypt. Their network is 'proxynet'. Now I would I go about accessing sonarr or radarr through the reverse proxy as well. I can't just change their network from none to 'proxynet' can I? My goal is to access these containers from sonarr.* and radarr.* from the internet.

I came across this in my letsencrypt container log. It's the only highlighted text and everything seems to be working ok, but I don't want to be complacent. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) I'm currently trying to resolve some nextcloud iOS app camera roll upload issues and just making sure this isn't related.

This software is great. I've got it setup as per OP and works fine. My goal is a 100% paperless household. Most of my source of paper is mail and doctor visits. Any suggestions on: What is the best budget home scanner to use for duplex scanning? How best to handle the work flow after the scan is consumed Do you just leave it in there and use search? Do you sort it by tag/correspondent to automatically move it to nextcloud? Other ideas? Just looking for practical advice from other users that may have dialed in the workflow and are really happy with it.

It's pretty pretty awesome considering. I would say maybe adding a time stamp or elapsed time on build in the log would be good to benchmark and identify anything odd. You mentioned some expected build times in your post, so I thought that would be good. But really if you read the log it's sufficient to see what happened. So again. not really it's pretty awesome. Already deleted!

Big big thanks to ich777 for this container + instructions. Also big thanks to rachid596 for providing this AMD USB/Audio fix patch from reddit. Such a gamechanger. Love this community. Was able to build this in ~10min with a full core workout. The log showed successful patch of AMD function level reset fix ./ quirk_no_flr.patch sent 2,302 bytes received 38 bytes 4,680.00 bytes/sec total size is 2,168 speedup is 0.93 ---Applying patches to Kernel, please wait!--- patching file drivers/pci/quirks.c Hunk #1 succeeded at 3719 with fuzz 2 (offset -23 lines). Hunk #2 succeeded at 4877 with fuzz 1 (offset 288 lines). patching file drivers/ata/libata-core.c Hunk #1 succeeded at 2388 (offset 1 line). Hunk #2 succeeded at 2481 (offset 4 lines). Hunk #3 succeeded at 2534 (offset 4 lines). Hunk #4 succeeded at 2559 (offset 4 lines). Hunk #5 succeeded at 2655 (offset 5 lines). patching file drivers/scsi/hpsa.c Hunk #1 succeeded at 978 (offset 2 lines). patching file drivers/scsi/mvsas/mv_init.c Hunk #1 succeeded at 655 (offset -31 lines). patching file fs/reiserfs/resize.c patching file fs/reiserfs/super.c patching file arch/x86/kvm/x86.c Hunk #1 succeeded at 116 with fuzz 1 (offset 7 lines). patching file include/linux/blkdev.h Hunk #1 succeeded at 1165 with fuzz 2 (offset -159 lines). patching file drivers/pci/quirks.c Hunk #1 succeeded at 3564 (offset 173 lines). patching file include/linux/pci_ids.h Hunk #1 succeeded at 1797 (offset 13 lines). patching file lib/raid6/algos.c Hunk #1 succeeded at 28 with fuzz 2 (offset -5 lines). Hunk #2 succeeded at 234 (offset 9 lines). Hunk #3 succeeded at 319 (offset 15 lines). patching file drivers/pci/quirks.c Hunk #1 succeeded at 5238 (offset 109 lines). And now I'm rocking and rolling in plex with nvidia and got my Win10 VM with USB hub + audio passthrough working. Life is good. 2020-07-01_05.29.38.log quirk_no_flr.patch