scud133b

Members
  • Posts

    73
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

scud133b's Achievements

Rookie

Rookie (2/14)

9

Reputation

  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.subdomain.conf myapp.subdomain.conf authelia-server.conf authelia-location.conf For #1, I have set up the subdomain for authelia and verified that it works -- CNAME set correctly and can access authelia directly as expected. For #2, myapp works correctly on its own when unprotected. To enable authelia protection, I have uncommented the two relevant lines so that myapp includes #3 and #4 in its proxy config. For #3, I have it set up exactly according to the authelia sample on github, lines 1-30, with the only changes being I put the actual server IP and authelia port into the appropriate placeholders. And lastly #4 is changed only to remove /api/verify from location in the LSIO default, because that is already a part of #3 per the default config from authelia. So now the first line reads: auth_request /authelia; which means this file matches lines 36-42 of the github example. And now I'm getting these nginx errors: "invalid port in upstream "http://[server ip]:[authelia port]/authelia/api/verify," "auth request unexpected status: 500," Any suggestions for why it says the port is invalid? I noticed that lines 33-34 and lines 44-69 don't appear to be covered in any of these four files, but it also appears the LSIO has set up some slightly different variables than the default Authelia config so I'm not sure. TL;DR: Authelia works fine in SWAG independently, my app works fine in SWAG independently, but when I try to have my app protected by authelia i'm getting the upstream port error, above.
  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-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] nginx-proxy-manager.sh: executing... [cont-init.d] nginx-proxy-manager.sh: Starting database... [mysqld] starting... 2020-04-14 19:27:17 0 [Note] /usr/bin/mysqld (mysqld 10.3.22-MariaDB) starting as process 359 ... 2020-04-14 19:27:17 0 [Note] InnoDB: Using Linux native AIO 2020-04-14 19:27:17 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-14 19:27:17 0 [Note] InnoDB: Uses event mutexes 2020-04-14 19:27:17 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-04-14 19:27:17 0 [Note] InnoDB: Number of pools: 1 2020-04-14 19:27:17 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-04-14 19:27:17 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-04-14 19:27:17 0 [Note] InnoDB: Completed initialization of buffer pool 2020-04-14 19:27:17 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] nginx-proxy-manager.sh: executing... [cont-init.d] nginx-proxy-manager.sh: Starting database... [mysqld] starting... 2020-04-14 19:27:17 0 [Note] /usr/bin/mysqld (mysqld 10.3.22-MariaDB) starting as process 359 ... 2020-04-14 19:27:17 0 [Note] InnoDB: Using Linux native AIO 2020-04-14 19:27:17 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-14 19:27:17 0 [Note] InnoDB: Uses event mutexes 2020-04-14 19:27:17 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-04-14 19:27:17 0 [Note] InnoDB: Number of pools: 1 2020-04-14 19:27:17 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-04-14 19:27:17 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-04-14 19:27:17 0 [Note] InnoDB: Completed initialization of buffer pool 2020-04-14 19:27:17 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-04-14 19:27:17 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2020-04-14 19:27:17 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2020-04-14 19:27:17 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2020-04-14 19:27:17 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2020-04-14 19:27:17 0 [Note] InnoDB: 10.3.22 started; log sequence number 2894528; transaction id 29983 2020-04-14 19:27:17 0 [Note] InnoDB: Loading buffer pool(s) from /config/mysql/ib_buffer_pool 2020-04-14 19:27:17 0 [Note] InnoDB: Buffer pool(s) load completed at 200414 19:27:17 2020-04-14 19:27:17 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-04-14 19:27:17 0 [Note] Server socket created on IP: '::'. 2020-04-14 19:27:17 0 [Note] Reading of all Master_info entries succeeded 2020-04-14 19:27:17 0 [Note] Added new Master_info '' to hash table 2020-04-14 19:27:17 0 [Note] /usr/bin/mysqld: ready for connections. Version: '10.3.22-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server [cont-init.d] nginx-proxy-manager.sh: Upgrading database if required... [cont-init.d] nginx-proxy-manager.sh: Shutting down database... 2020-04-14 19:27:18 0 [Note] /usr/bin/mysqld (initiated by: unknown): Normal shutdown 2020-04-14 19:27:18 0 [Note] Event Scheduler: Purging the queue. 0 events 2020-04-14 19:27:18 0 [Note] InnoDB: FTS optimize thread exiting. 2020-04-14 19:27:18 0 [Note] InnoDB: Starting shutdown... 2020-04-14 19:27:18 0 [Note] InnoDB: Dumping buffer pool(s) to /config/mysql/ib_buffer_pool 2020-04-14 19:27:19 0 [Note] InnoDB: Buffer pool(s) dump completed at 200414 19:27:19 2020-04-14 19:27:19 0 [Note] InnoDB: Buffer pool(s) dump completed at 200414 19:27:19 2020-04-14 19:27:20 0 [Note] InnoDB: Shutdown completed; log sequence number 2894537; transaction id 30003 2020-04-14 19:27:20 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2020-04-14 19:27:20 0 [Note] /usr/bin/mysqld: Shutdown complete chown: /config/log/nginx/nginx: No such file or directory [cont-init.d] nginx-proxy-manager.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting statusmonitor... [services.d] starting logrotate... [statusmonitor] no file to monitor: disabling service... [services.d] starting logmonitor... [services.d] starting mysqld... [logmonitor] no file to monitor: disabling service... [logrotate] starting... [mysqld] starting... 2020-04-14 19:27:47 0 [Note] /usr/bin/mysqld (mysqld 10.3.22-MariaDB) starting as process 31753 ... 2020-04-14 19:27:47 0 [Note] InnoDB: Using Linux native AIO 2020-04-14 19:27:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-14 19:27:47 0 [Note] InnoDB: Uses event mutexes 2020-04-14 19:27:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-04-14 19:27:47 0 [Note] InnoDB: Number of pools: 1 2020-04-14 19:27:47 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-04-14 19:27:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-04-14 19:27:47 0 [Note] InnoDB: Completed initialization of buffer pool 2020-04-14 19:27:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-04-14 19:27:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2020-04-14 19:27:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2020-04-14 19:27:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2020-04-14 19:27:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2020-04-14 19:27:47 0 [Note] InnoDB: Waiting for purge to start 2020-04-14 19:27:47 0 [Note] InnoDB: 10.3.22 started; log sequence number 2894537; transaction id 29983 2020-04-14 19:27:47 0 [Note] InnoDB: Loading buffer pool(s) from /config/mysql/ib_buffer_pool 2020-04-14 19:27:47 0 [Note] InnoDB: Buffer pool(s) load completed at 200414 19:27:47 2020-04-14 19:27:47 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-04-14 19:27:47 0 [Note] Server socket created on IP: '::'. 2020-04-14 19:27:47 0 [Note] Reading of all Master_info entries succeeded 2020-04-14 19:27:47 0 [Note] Added new Master_info '' to hash table 2020-04-14 19:27:47 0 [Note] /usr/bin/mysqld: ready for connections. Version: '10.3.22-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server [services.d] starting nginx... [services.d] starting app... [nginx] starting... [app] starting Nginx Proxy Manager... [services.d] done. [services.d] starting nginx... [services.d] starting app... [nginx] starting... [app] starting Nginx Proxy Manager... [services.d] done. [4/14/2020] [7:27:49 PM] [Migrate ] › ℹ info Current database version: 20190227065017 [4/14/2020] [7:27:49 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [4/14/2020] [7:27:49 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [4/14/2020] [7:27:49 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [4/14/2020] [7:27:49 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [4/14/2020] [7:27:49 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [4/14/2020] [7:27:49 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [4/14/2020] [7:27:49 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [4/14/2020] [7:27:49 PM] [Global ] › ℹ info Backend PID 31823 listening on port 3000 ... `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0
  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/proxy_host/ this new config file is NOT there. So it looks like maybe the database thinks it created the proxy config, but it never actually generated and saved the file correctly.