minimos

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by minimos

  1. Hi, So I finally figured it out. It looks like there was an unintentional power loss rebooting my server. For some reason the modprobe i915 setting was not in my 'go' config, not sure why as I am sure I added it on server build last year. However my server had been running 24/7 for over 12 months prior to last week with no reboots. I figured this out by starting the docker from the terminal using 'docker start' command, which complained of no /dev/dri for hardware transcoding. The 'Power Loss' also explains why my main desktop PC stopped posting late last week (lines up with my Unraid uptime and my wife telling me the 'PC is broken it just went off'). I'd just assumed the old z270 board and 6700k had bit the dust with the latter being nearly 6 years old. At least I have a z690 and i12600k now though as a shiny replacement, which I could not have justified before. 😀 Hope this info helps others in the future.
  2. Hi @Squid Thanks for posting. Here is the output of the docker run command. It appears to complete successfully. I also tagged to an earlier build in this output, but still have the same issue. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='binhex-plexpass' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/tmp/' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/Curated Photos/':'/Photos':'ro' -v '/mnt/user/Music/':'/Music':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' --device='/dev/dri' 'binhex/arch-plexpass:1.26.0.5715-1-01' 34bf46ef5afdbed64debd4a670c313911b64c27d9bc51515acdca098681ea4b0 The command finished successfully!
  3. Hi, I have an issue with the docker container. I've had it happily running for over 12 months taking in regular updates but suddenly the container has stopped and will not start. Other docker containers start normally and run, but attempting to start it up brings up an Execution Error Server Error. No logs appear to be created in either Unraid or the appdata directory. I was wondering whether it was down to a recent update. Is anyone able to assist? Thanks in advance
  4. So I have managed to improve on the solution above and get the docker container name working in the Nginx config file, which further increases security by making make the http request stay internal to the docker network and not leak onto my wider LAN. The trick is to specify a variable PAPERLESS_ALLOWED_HOSTS, in the docker setup. Add it as a new environment variable. Then, you have to specify both your custom domain name and the docker container separated by a comma. You have to put your custom domain first or you will get 400 HTTP codes in paperless for some content, so the new variable value would be 'paperless.example.com,paperless-ng', substituting example.com for whatever your custom url is. Update your Nginx subdomain config variable $upstream_app to 'paperless-ng' or whatever your contain is and restart Swag and it should all be working. Hope others find this useful
  5. Finally got it resolved, thanks to a solution earlier in the thread from @muppie & @Lumpy_BD. I used the config on page 4 substituting the ip address on the $upstreamapp variable for my own Unraid host IP. However, before this, I cleared up the error above by removing the suggested Nginx settings from the paperless-ng documentation and the django error cleared up, but I still got a bad gateway message until I made the ipchange Hope this might help someone else
  6. Hi, Thank you so much for coming back with info. I've done a bit more digging, and have decided to use swag (which includes nginx) as my reverse proxy as it has a few other nice features and moved the swag container an paperless-ng to the same docker network (to stop network leakage) I have got swag up and running with a cert being pulled for my domain, however I can't for the life of me get it to work. I keep getting a a 502 error (Bad Gateway), when using my subdomain to access the server. SWAG works fine with the sub domain connected (i.e I get the default SWAG page) if I don't have a subdomain configured in Nginx. I also included the suggested Nginx configuration from the original paperless project but I still get the same error. EDIT: Found an error in the Paperless Log '[ERROR] [django.security.DisallowedHost] Invalid HTTP_HOST header: paperless.example.com, paperless.example.com The domain name provided is not valid according to RFC 1034/1035.' It seems to indicate that the domain name is being passed twice in the header (host example changed from my own domain for security reasons) Does anyone potentially have any ideas on what I could check? Thanks Minimos
  7. Hi, I'm looking for some help to secure my installation of paperless-ng. I have seen mentions of setting up Nginx or Swag as a reverse proxy to serve up the app over SSL, but I'm a little bit stumped on how to do this. I do not intend to expose my docker instance of paperless-ng to the internet (although it might be something I tinker with later), however all the requests to the server are http, which means my user name, and any other information can be intercepted and read using something like Wireshark (I know this would mean someone snooping with access to my network already so is an unlikely event), but I feel all comms of sensitive data should really be secured, Secondly, if I was to setup a reverse proxy, my encryption is to the proxy from what I understand, and the comms from proxy to the docker container would still be unencrypted and susceptible to snooping also? Can anyone provide some steps / hints on how I configure the docker contain to run as https for all requests? Thanks in advance Minimos
  8. Thanks for the explanation. I'm assuming then that an SSD cache drive will help negate some of the performance hit for writes, and you configure to allow a VM to puts its virtual disk there?
  9. Hi, Thanks for the feedback. Genuine question, would running more disks and having a parity drive really impact CPU to a high degree? I know there will be some overhead, but I'm seeing 25 - 30% average consumption with 2 Plex streams Transcoding and a Windows 10 VM spun up. I'm trying to understand potential costs, and I don't really want to spend on storage until I've bit the bullet and worked out the other components, especially as some drives will come across from my existing build
  10. Hi, I am looking at building an Unraid server to replace an existing W2k12 Essentials Server (AMD Turion II N54L with 10GB RAM) that acts as a domain controller for my home network. The current server is holding up well for something that is nearly 7 years old, but as my needs have grown it beginning to creak and groan under the load (especially disk IO). It is also not setup in the most ideal way (i.e it is installed bare metal with additional virtual machines running in Virtualbox), but it serves its purpose of running a DC, File and Backup Server, Pi Hole, Plex and a Grafana/InfluxDB VM for logging various IOT device attributes in my home. I'm usually like to tinker rather than jump in and regret my decisions later, so I have setup a build using an old i7 3770k and ASRock Pro 4 motherboard with 16GB RAM and 1 old 2TB HD to get a feel of how Unraid would perform. I've configured a new instance of Plex as a Docker container and enabled hardware transcoding through the CPU, I've also installed Win 10 as VM, URBackup and it doesn't really break a sweat, so CPU wise I appear to have enough compute, however as its an unlocked CPU edition it does not allow the use of IOMMU to pass-through a GTX 970 I have lying around. What I'd like is some suggestions on Motherboard and CPU that would give me full IOMMU support, and some potential scope for the future without breaking the bank. Ideally I'd also look at getting new kit as I plan on building this and letting it run for at least another 7 years. Thanks in advance Minimos