Abe677

Members
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Abe677's Achievements

Noob

Noob (1/14)

4

Reputation

  1. I feel like an idiot but some confusion on my part lingers. Just did a vanilla install of the InfluxDB docker on my up-to-date Unraid server. I didn't change anything since the default ports 8083 and 8086 were unused. When I attempt to connect via the "WebUI" context menu I get a "ERR_CONNECTION_REFUSED" error. So I google a bit and read some posts that the web UI has been depreciated and I should use console commands, but that goes nowhere. I see that the WebUI context menu is using port 8083. For the heck of it I change it to port 8086 and voila - a web UI that lets me set up InfluxDB. So is the Web UI depreciated? Is there was port swap in the docker template?
  2. Guessing here. The document date is being picked up via something it thinks is a document date after OCRing it. I suspect if you look at the document properties in p-ngx you might see the connection. I have my new documents tagged with "inbox" automatically so I can easily find them when I use the web app. Then I can update the metadata and remove the inbox tag.
  3. Unraid 6.11.5, Docker version status for paperless-ngx has been "not available" for around a day. I update these things routinely so it's odd. db-backup docker also in this state but only those 2 (of 20). Repo says "ghcr.io/paperless-ngx/paperless-ngx". Best I can tell it's still there. UPDATE: Installed the CA Docker Patch plugin and all seems well again.
  4. I see there at least a couple of posts about this, but no explanation. I just upgraded from 6.9.2 to 6.11.5 and also see the stream counts are always zero. In 6.9.2 the stream count was somewhat useful for determining what shares were in use. Also a good post-reboot sign that things were working. Now that the stream count is always zero, I'm not sure what to make of it? Bug? Feature? Things seem to be working on my server so I can't say anything is broken. (Upgrade was easy by the way - thank you!)
  5. I updated from ng to ngx some time ago. I'm using dyndns and have things set so I can go to: site.my_domain.dyndns.org I have NGINX running and have paperless.my_domain.dyndns.org pointing to my unraid server IP address port 8001. While on my LAN, https://<unraid_server_ip_address>:8001 works as you'd expect. Works great. When outside my LAN, paperless.my_domain.dyndns.org -> NGINX gets me to the paperless credentials login page, but after I enter my usual username and password I get a long pause followed by "504 Gateway Time-out" and "openresty" underneath that message. I have the paperless app on my android phone. It's been "logged in" forever and seems to work. Turned off the wi-fi. Still works. I logged out of the paperless app, then back in. Used https://paperless.my_domain.dyndns.org. Entered my credentials. Get an error 504 after a long time. Kill the android process. Start the paperless app again and I can see my documents. I've checked the NGINX and paperless-ngx docker logs and don't see an error message. Browser access from outside my house would be useful. The phone app behavior seems odd. (I don't expect phone app help or support here, just providing information.) Wondering if there's a guide or post on how to do this "right" because I'm obviously missing something.
  6. My Docker default is set to "/mnt/user/docker/appdata/". The following containers are using this path: mariadb (/mnt/user/docker/appdata/) PlexMediaServer (/mnt/user/docker/appdata/) QDirStat (/mnt/user/docker/appdata/) nextcloud (/mnt/user/docker/appdata/) binhex-krusader (/mnt/user/docker/appdata/) Handbrake (/mnt/user/docker/appdata/) The following have no appdata that I can tell: Redis (none) OpenSpeedTest (none) db-backup (none) The following have a appdata path different than the default: bookstack (/mnt/user/bookstack/) paperless-ng (/mnt/user/appdata/paperless-ng/data) Nginx (/mnt/user/NGINX/) Influxdb (/mnt/user/appdata/influxdb) I suspect I was following various tutorials to set these up and wasn't aware all the container "appdata" data needed to be in one place. The good news is that the 4 containers that are not set up correctly could be nuked and set up properly. I suppose if I was clever I could shut those containers down, move that data to the proper location, change the container setting, and they should start. I'll have to think about this.
  7. I've been trying to search this topic without much luck. I'd like to run this plug-in. I'd sort of a Unraid rookie. I have an appdata share and when I look at its contents I don't see folders for every docker I'm running. When I edit each docker and look around, I see I have appdata folders "spread around." So a few questions come up. If I do nothing, with this plug-in find the appdata folders for each docker and back them up regardless of their location? Do I need to fix this appdata location problem? If so, is the only solution re-installing each docker while paying more attention to where the appdata folder end up?
  8. Adding my interest here. I would like to be able to backup one Unraid server to another over the internet. Being able to throttle bandwidth use would be a must, and a bonus would be the ability to schedule the activity in some way. For example, there may be certain times of the day when I wouldn't want the backups to consume any bandwidth, but when everyone is sleeping "release the hounds" (with possible bandwidth limits even then). (Thanks to the person who mentioned the rsync throttle feature, which I was not aware of.)
  9. I can't answer your specific question about inotify on Unraid. I'm playing with Paperless-ng on my Unraid server and it seems to see and process files in the consume folder with no problem. I would describe my experience this way - Paperless-ng works great on an Unraid server, and you will spend more time thinking about things like tags and workflow than actually getting it to work.
  10. Yes you are completely correct. I hadn't thought to look at the original project. Thanks!
  11. This is a Paperless-ng use question. Have it running on Unraid. If this isn't the right place to ask feel free to delete my post. I know once my document is consumed I can use the web UI to tag my document. I've looked at the suggested work flow. What I'm not clear about are the file name requirements for the scanned documents? There's a brief note about Paperless-ng using the file name to determine things about the document before it does an OCR and other processing, but I haven't stumbled on any suggested file naming for the scanned documents that are going to be pushed to the consume folder. Is there any magic there or does it really not matter? (Maybe the answer is different depending on whether I'm scanning and shredding vs archiving?)
  12. I’m new to Unraid, docker and many things here. I need some education or a pointer to some education. I’m going to use my desire to run BookStack as an example. Easy enough to find BookStack via Community Applications. When I click to install I’m faced with having to provide some information. Since I don’t have much experience I’m looking for some pointers on where to go to figure out what all those container settings should be? I watched a youtube video on someone installing BookStack via Portainer. In that video it appears the installation creates the BookStack app and the database to support it. However when I click to install on my Unraid server there’s a very clear “A database server is needed.” This leads to a series of rookie questions: 1. What database should I install? (I assume I need to install it first.) 2. Does the BookStack app take care of doing all the database work or is there some database configuration that’s required before BookStack is installed? I run into this information void with every docker I install. Sometimes I can find a good walk-thru document or video that helps, but so far I haven’t run into anything too helpful for BookStack on Unraid. Just looking for some pointers to how people track these answers down?
  13. Consuming /consume/P4400 Kill A Watt Operation Manual.pdf ** Processing: /tmp/paperless/paperless-x6exs9yt/convert.png 439x571 pixels, 16 bits/pixel, grayscale Input IDAT size = 436899 bytes Input file size = 437112 bytes Trying: Selecting parameters: zc = 9 zm = 9 zs = 3 f = 4 IDAT size = 435698 Output file: /tmp/paperless/paperless-x6exs9yt/optipng.png Output IDAT size = 435698 bytes (1201 bytes decrease) Output file size = 435755 bytes (1357 bytes = 0.31% decrease) Processing sheet #1: /tmp/paperless/paperless-x6exs9yt/convert-0000.pnm -> /tmp/paperless/paperless-x6exs9yt/convert-0000.unpaper.pnm [pgm_pipe @ 0x564da79becc0] Stream #0: not enough frames to estimate rate; consider increasing probesize [image2 @ 0x564da79c0100] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [image2 @ 0x564da79c0100] Encoder did not produce proper pts, making some up. OCRing the document Parsing for eng Language detection error: No features in text. Language detection failed! As FORGIVING_OCR is enabled, we're going to make the best with what we have. Unable to detect date for document d Document 20200906082154: P4400 Kill A Watt Operation Manual consumption finished
  14. Didn't make a difference. The document in question was a paper document that I scanned on my flatbed scanner, so there's no embedded text in this PDF. It's a PDF with an image in it.
  15. Just installed Paperless on my Unraid server today. I love the idea of this application! Installation post says, "4.3 Remove the port to avoid port conflicts with the webserver" and I wan't sure if this meant deleting the port number or using the "Remove" button for the variable. I used the "Remove" button and things seem to work. Maybe someone else will also be unsure and see this post. My logs time zone is wrong, so it's not passing my server time zone. Reading posts here I'm confused about this. For now I've added: PAPERLESS_TIME_ZONE: US as a variable to the consumer docker setup. The consumer docker failed because it didn't like "US". I need to figure this one out. UPDATE: Set PAPERLESS_TIME_ZONE to "America/New_York" without quotes for the Paperless docker, not the consumer docker. This seemed to fix the logs. I'm a little surprised by the OCR situation so far. The first scan I processed was a 1-page PDF of instructions for one of those "Kill A Watt" devices. I would have thought the OCR would do well with it but initially it failed because it didn't see "english". I changed PAPERLESS_FORGIVING_OCR to true so it would process the pdf, which is did, but no good OCR. I also tried a scan of a 1-page magazine article and the results were also not good. Other PDFs and jpgs seemed better. UPDATE: I had previously scanned a obituary which was a newspaper clipping. I had scanned it as both a jpg and PDF. No OCR for the PDF but OCR for the jpg was pretty good. Puzzling to me.