SimplifyAndAddCoffee

Tempting but sounds risky. Is there even a way to pool the disk without losing the data that is currently on it? I have a ton of dockers and a VM all dependent on that disk.

Setting user permissions... Modifying ID for nobody... Modifying ID for the users group... Adding nameservers to /etc/resolv.conf... Extracting packaged nessus debian package: Nessus 8.10.0... Changing owner and group of configuration files... Creating symbolic links... Cleaning up... Starting Nessus : . [Thu Feb 4 11:00:52 2021][30.1][op=_qdb_map][name=services-udp.db][fd=-1][map_sz=38575]: complete [Thu Feb 4 11:00:52 2021][30.1][op=_qdb_map][name=services-tcp.db][fd=-1][map_sz=40899]: complete [Thu Feb 4 11:00:52 2021][30.1][op=_qdb_map][name=services-tcp.db][fd=-1][map_sz=40899]: complete [Thu Feb 4 11:00:52 2021][30.1][op=qdb_sync][name=upgrades.db][fd=5][map_sz=0][file_size=55]: complete [Thu Feb 4 11:01:02 2021][30.23][sched=100][pid=53][plugin=nessusd_www_server6.nbin][instr=0xd779] : Error: Could not find function 0xf000020c call stack: ----------- [0d779:Socket.accept+36] call, addr(0xf000020c), -, # ???? () [C func] [07bb2:Mug::Connection.on_client+46] refcall, fp(2), string#707, # from: fp(2) [22d1e:!anon5+4] refcall, fp(-2), string#4934, # from: fp(-2) [2eb54:main+10121] eop, -, -, [Thu Feb 4 11:01:14 2021][30.1][op=qdb_sync][name=plugins-desc.db][fd=19][map_sz=0][file_size=187756524]: complete [Thu Feb 4 11:01:14 2021][30.1][op=qdb_sync][name=plugins-code.db][fd=7][map_sz=0][file_size=2967368547]: complete [Thu Feb 4 11:02:05 2021][30.1][op=_qdb_map_lowmem][name=plugins-code.db.16124364741952786213][fd=7][map_sz=0][file_size=2967368547]: complete [Thu Feb 4 11:02:08 2021][30.1][op=_qdb_map_lowmem][name=plugins-desc.db.1612436525562718452][fd=19][map_sz=0][file_size=187756524]: complete similar issue to above poster. I last ran this back in november and it worked fine, but now it fails to update plugins or run scans.

I have a UD disk that I am running my dockers on. I want to know if there is a way to create custom mount points and shares on the UD disk and control access via SMB users. When I share the UD disk, it creates a public share at \\server\Patriot_Blaze_DE3F07580DC602009379\ I do not want it public, and I also don't want it named Patriot_Blaze_DE3F07580DC602009379. There are a couple things I am hoping to do with this: I want to be able to run an rsync cron job to back up the contents of the UD disk to /mnt/user/backup/docker I would like to rename the disk, if possible I want to be able to mount and share arbitrary directories within the UD disk, for example /mnt/disks/Patriot_Blaze_DE3F07580DC602009379/appdata/swag/www as \\server\www only visible to specific samba users I want to be able to mount shares to arbitrary directories within the UD disk, for example I want to mount /mnt/user/media (or \\server\media) to /mnt/disks/Patriot_Blaze_DE3F07580DC602009379/appdata/swag/www/media I want to be able to persist all of this What would be the way to go about this?

Yes, and I can reach it locally using http://server:8086 I am using http validation, but I could theoretically change that if I have to. My local DNS is managed at the router. For configuring nginx, would that be done in the subdomain.subdomain.conf file? or is there a way to manage specific upstream hosts elsewhere in nginx? Any information on how to do that would be helpful, since I'm new to nginx (and docker in general). EDIT: I got it sorted. Didn't realize the container and app used different ports.

I'm trying to use this with SWAG/nginx and there are 2 problems I'm having trouble solving: 1. I get a 502 bad gateway using the subdomain to try and hit the bitwardenrs docker on 8086. ## Version 2020/12/09 # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url # make sure your bitwarden container is named "bitwarden" # set the environment variable WEBSOCKET_ENABLED=true on your bitwarden container server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; 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 bitwardenrs; set $upstream_port 8086; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /admin { # 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 bitwardenrs; set $upstream_port 8086; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwardenrs; set $upstream_port 3012; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app bitwardenrs; set $upstream_port 8086; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } 2. I don't want bitwarden exposed to the internet, despite the fact I am also using the reverse proxy to handle internet traffic to other dockers. Is there any way to configure this so that BitwardenRS gets SSL on the LAN but can't be reached from the WAN?