scud133b

Members
  • Content Count

    73
  • Joined

  • Last visited

Community Reputation

9 Neutral

About scud133b

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. This is true but I discovered one slight modification; redis doesn't usually have a username so you actually leave it blank before that colon. So it will be: redis://:password@[IP]:6379
  2. Yep it's under Settings > Docker > Advanced View and has a help tooltip. But I would never have known it was there without you guys nudging me to look for it. Google still turns up a bunch of older info from all the usual places (unraid wiki, forums, reddit, etc.) that says user defined bridges aren't possible in unraid. The question often comes up in context of using docker-compose so perhaps the older comments are more about that, but in short, I turned up empty on my research.
  3. For paperless-ng, is there an environment variable for a redis password? I've been searching for a while now and can only find detail about the one variable to specify the redis host, but not the password.
  4. I did and @aptalca helped me out. Didn't realize you *could* make user defined bridges in unraid, all my google searches turned up that it wasn't possible. Unraid docs need updating I think. Revised my previous post.
  5. EDIT: This was all made moot by moving my external facing docker containers to a user defined bridge per the Unraid section of these instructions: https://github.com/linuxserver/reverse-proxy-confs#ensure-you-have-a-custom-docker-network. It is possible! Leaving the rest of the post here for posterity. Hi everyone, I'm still working on getting Authelia & SWAG to be happy. Because we're talking Unraid I can't use the user defined bridge network, so I'm trying to set it up with the subdomain config. I now have four different files I'm working with: authelia.su
  6. @TX_Pilot Can you explain a little more about how you achieve #2? With "creating an internal Docker network for your reverse proxy and specifying container names". Right now my whole system is in Bridge networking but I love the idea of using variables, as you have here... I'm sure there will be a reason my future-self will appreciate that.
  7. Something like this could become very useful with Google Photos changing. Do you know if they intend to have mobile upload, sharing, etc? Seems like the use case is more for a professional (?) who backs up from a memory card to a directory on the server. Don't see a single file upload so I guess you have to find a way to get everything into the monitored directories.
  8. Anyone had success with the built-in Collabora environment (CODE) in v19.x? I'm having trouble connecting to the new built-in CODE server and I wonder if it has something to do with nginx config. I'm using nginx proxy manager so I'm not sure how to properly edit the config to allow access, e.g. according to this post: https://www.collaboraoffice.com/online/connecting-collabora-online-built-in-code-server-with-nginx/
  9. So I gathered that the drives might be accessed during the test so I actually shut down all VMs and all other docker containers (so this was the only thing running) and that produced the test results you saw in my post. I haven't had a chance to try swapping disks between the onboard controller and the PCIe controller but I can do that next if you think it might illuminate something. Thanks
  10. Hi @jbartlett this is a really cool tool, thank you. The tests are finding a few problems. Note that Disk 4 is on the onboard controller and the others are on a SAS HBA card. First, the app reports a bandwidth cap error on all my SATA drives. Second, I'm getting frequent Speed Gap notices when I run the all-disk benchmark. Third, the graph appears to be pretty shaky/wobbly for several of my disks. I attached a shot of the graph. Any suggestions for what is causing this behavior?
  11. And now another fun finding: I got the entire process to work by doing it in Chrome. So apparently the errors happening in the Brave browser prevented the proxy host from being fully created -- but doing it in Chrome worked fine. So I'm all green again and everything's working now. *shrug*
  12. Another data point: it appears the app never correctly saved the certificate for my new proxy host. The error refers to the folder /etc/letsencrypt/live/npm-14/.... and that isn't in the file system. I see the other folders for other proxy hosts (like npm-3, npm-5, etc.) but not npm-14. So for some reason the new SSL cert and the associated files are not being saved in the appdata folder for any new hosts I try to create.
  13. Also using Brave and you're right. Works fine in Chrome. I only changed the http/https ports (e.g., the container gets ports 1880 1443) and I have my router properly forwarding to them. That config has been totally fine until I tried to create a new proxy host this week.
  14. In case it helps here's an example log I just grabbed: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-
  15. In my case -- no changes to the container config beyond changing ports to avoid conflicts. I tried downgrading to v1.7.0 and now I have another issue -- I can't actually load the Proxy Hosts page in the UI anymore. Click the link and nothing happens... the other pages work fine (Redirection Hosts, Streams, 404 Hosts). The browser address bar even updates to the correct address (http://server:port/nginx/proxy) but nothing on the page changes at all. So that's fun, doesn't seem related but maybe it is (?). Edit: I should add that when I actually view the files in /nginx/p