tmor2

That's not what it means. I checked few apps I have installed including swag... None other icons have red star. All installed apps have a "EDIT" icon on lower left, vs "DOWNLOAD" icon (for uninstalled icons).

I noticed two Resilio apps listed by linux server. Is the one with the star deprecated? How do I switch from the one on the right to the one on the left ? (-given they are both linux, can i simply edit docker-template under advanced?)

Thank you. simple solution.

I recently unplugged USB cable from external HDD being mounted to UNRAID server via "Unassigned Devices". After I reattached the drive, the drive won't mount correctly. Attached pics show how this looks along with logs. Specific error message states: "Tower unassigned.devices: Mount of '/dev/sdh2' failed. Error message: FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option" I note recommendation to run "fsck" command. https://wiki.unraid.net/Check_Disk_Filesystems does not show how this command is used for exFAT formatted systems. Assuming that I'm using UNRAID terminal, what is the syntax for "fsck" command. I'd like to make sure that fsck is only run against that specific drive (and not my array drives), and I'd also appreciate to know where in directory structure within UNRAID terminal window do I need to be positioned when executing fsck cmmand. Namely, in UNRAID terminal this drive has following directory aisgnments: /dev/sdh and /mnt/disks/ Do I need to unmount the drive, then navigate to /dev/ and execute fsck against sdh? Suggestions?

If by diagnostics you mean "LOG" from here, these logs are empty. Are there other diagnostics?

That's fine, but Ext HDD/USB sticks will still be mounted as mnt/disks (Read Only option disabled) with exFAT formatted (yes, UA AND UA plus are installed). Is this on purpose? When USB-attached devices (USB stick, ext HDD) are mounted, then no files can be written to such external stores, eventhough permissions are set to rwx . Also, cannot format disk any longer. Switching to legacy support does not solve the problem. Previous plugins did not have this issue. What is solution for that issue? Btw, the SMB mounted shares work just fine, and yes they are mounted as mnt/remotes.

Solved. Problem was in appdata/bitwarden/config.json file. Second line should have started with "https" and not "http",.

Thanks, I understand what you are saying, and I read this page, however it does not reference SWAG docker, which is what I am using. I cannot reference such a user guide because I am interested in what works in practice, and not on paper (webpage). What happens in practice is following: Upon generation of certificates (when swag docker is restarted), the content in the following folder /mnt/usr/appdata/swag/KEYS/letsencrypt/ disappears (is deleted by swag docker) and then new files appear, namely all certificates newly issued. The certificates in that folder have timestamp that is few seconds older than when swag docker was restarted. In other words this statement from your refernce is simply NOT true: /etc/letsencrypt/archive and /etc/letsencrypt/keys contain all previous keys and certificates, while /etc/letsencrypt/live symlinks to the latest versions. /etc/letsencrypt/keys does not contain all previous keys, because I verified this ( looked at exitigng keys frst, then restarted swag server, and the new keys in this folder were definitvly different (along with file time stamp being newer). There were no traces at all from "old" certificates.. This may be how swag docker is implemented. Folder /mnt/user/appdata/letsencrypt/live/ has certificates only for cloud.mydomain.com....but for not other subdomains or other domains. When I point Poste.io to folder /mnt/usr/appdata/swag/KEYS/letsencrypt/, Poste.io correctly restarts, there are no more warnings on iOS/Mac devices such as "the identity of the server yyz.com cannot be verifiied....". The aforementioned error was occurring for all 3 mail domains, for over 1 year on all of my devices. So if your solutions works for you great (using Letsencrypt docker), but my solution works for me (using swag docker), as evidenced by resolution of the problem that prompted me to post to begin with, and might work for others using swag docker and poste.io.

Good. Check the file UNRAID/appdata/bitwarden/config.json file, 2nd line, "domain" If your domain doesn't start with https, change it so it does. Otherwise you won't be able to download to your smartphone/tablet/PC any uploaded attachements (to bitwarden identity or other sections).

I installed gaps over a year ago and last used in with a command line (old version didn't used to have WebGUI). I just deinstalled Gaps, and reinstalled it, and you are correct, advanced tab now shows: "http://[IP]:[PORT:8484]" I can only deduce that updates may not have correctly updated this since the "terminal-only" days app.

The guide may pertain to Letsencrypt docker (which is not maintained any longer and has been migrated to SWAG docker). Your screen shot has 4 lines, what is the FILE NAME (!) of the first path? Line ends with /liv....????? I assume it's fullchain.pem??? But that needs not be true because there is also priv-fullchain-bundle.pem file. Your screen shot (below) shows path to swag...as /mnt/user/appdata/letsencrypt/live/SUBDOMAIN.DOMAIN.COM/*.PEM In swag, this directory is empty -> if you SSH into it from Docker command line, it will be empty. The keys are stored in following directory: /mnt/usr/appdata/swag/KEYS/letsencrypt/*.PEM

In your UNRAID/appdata/bitwarden/config.json file, 2nd line, "domain"...does your value start with http or https?

Can you list things you did? E.g. Your DNS provider Did you add CNAME to your DNS provider (SUBDOMAIN.mydomain.com points to mydomain.com)? Does "A" record point to your IP address? In SWAG/Letsencrypt did you: Modify file in appdata->swag->nginx->proxy-conf/bitwarden.subdomain.config? If so, what did you modify? UNRAID->swag docker->Edit -> Added SUBDOMAIN to "Subdomain(s)" field? If so, check log of swag. Does the log end with "Server ready" message? Does log contain any errors? Does container name within bitwarden.subdomain.config file match the docker name? Both names must match. Did you make any changes to UNRAID/appdata/bitwarden/config.json file? If yes, what changes? How did you try to access Bitwarden? via smartphone or browser? Smartphone,...your server address should start with https (not http).

I haven't gotten Plex Pass yet, so I cannot confirm it works for Plex. I did add the path for HW acceleration driver for Jellyfin docker, but it is still transcoding without HWA. Maybe Jellyfin doesn't support HWA?

With default docker installation options, and once docker is running, when user clicks on WebGUI (UNRAID->Gaps-> icon click, select webGUI), an error message shows in browser (can't access site,..etc). Upon closer inspection of webgui address (in browser), the address started with https. Once the "s" was removed (leaving http), the webgui could be accessed. In short, when user installs Gaps in docker, the webgui should correctly open, - except, it doesn't. The error is in docker default install options: Install Gap Click "EDIT" Switch to advanced view WebUI line: https://[IP]:[PORT:8884] SSL Boolean: false 4 and 5 cannot be both set like this at the same time. Either line 4. is changed to http://[IP]:[PORT:8884] or Default value for line 5. set to "true" Also, "SSL Boollean" should be changed to something more meaningful to all users, such as "Enable https for WebUI". It is not clear what "SSL Boollean" means: SSL to WebGUI, SSL to TVDB or sth. else. Does that help?

At first, I could not access Gap's WebGUI. After tweaking, I figured out why. If Gap installed with default settings (SSL: false...etc), opening webGUI should not force https, but instead default to http.

How did you add this: Is this, Variable, Path, Prot, Label or Device? What did you do in letsencrypt to issue certificate (I issue one for bitwarden, nextcloudetc) Did you add in "Sudomains": "mail"? (next to "nextcloud,sonnar,bitwarden...") Did you have to do anthing else on DNS provider (my MX record is enabeld)? Did you have to add .config file within letenscrypt? I see no existing template when I navigate to /etc/letsencrypt/live I don't see the 3 .pem files. Why? There is only etc/letsencrypt/live/nextcloud.MYDOMAIN.COM folder, but the folder is empty

I have another issue...... When I was logging into webui, I received error that local domain 10.10.20.x was blacklisted and I need to wait 2 days to release the block. Are there suggestions on how to overcome that block? thx

Hi. Letsencrypt (the docker) is used as a reverse proxy. Thus, when Bitwarden is invoked from outside of local network and via my subdomain bitwarden.mydomain.com, the request is routed to my letsencrypt (reverse proxy), which then routes rwuest to Bitwarden docker app. I am able to upload any attachment to Bitwarden (regardless whether I am local or on the go). I can see encrypted attachments in UNRAID->appdata->bitwarden->attachments (folder). However, whenever I use client on iOS/iPad or a browser plugin (any browser), or standalone OSX app, I simply cannot download/view that attachment. I reviewed the log from Docker->Bitwarden...It doesn't show any error messages, not even a request to access the attachment. Does that help?

Ops. I don't have Plexpass. I'll get one though.

Hi. Thanks for posting detailed guide. I have i-8700 with ASUS B360-I I could not get hw to work. My Bios: iGPU is enabled terminal commands in UNRAID execute correctly. edited Plex container and added Drive with mapping Name: /dev/dri Value:/dev/dri Transcoding doesn't show (hw) Also tried Name: /dev/dri Value:/dev/dri/ (note ending forward slash which was auto added, since I picked the folder from a dropdown list) doesn't work. Also tried Name: /dev/dri/ Value:/dev/dri/ doesn't work. Any help?

mullvad

Thank for the try. This app does not work. It cannot be configured to run with either Wireguard or OpenVPN, with a major VPN provider. App deleted.

All IP addresses are IPv4.

It didn't work.