tmor2
-
Posts
87 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by tmor2
-
-
{SOLVED}
Old USB for UNRAID is dead.
Installed UNRAID on a new USB, with UNRAID USB creator, plugged it in, and server starts in BIOS mode everytime. New USB is listed under BOOT menu, and no other settings in BIOS were changed. How do I solve this?
[SOLUTION]
On mac Catalina, the UNRAID USB Creator does not work!
Use manual method instead starting at 5:21 minutes:
-
On 2/16/2021 at 7:54 PM, Karyudo said:
Another unRAID problem that I don't know how to fix....
I tried to copy a bunch of data (100+ GB) from an unassigned drive to an unRAID share. Everything copied except for one folder. I went into Main to see what the remaining space was like on the array and on the UD. The array drive data showed there should be space available. The Unassigned Devices section showed nothing: not "no space"; no drives. That seemed weird. I think I then clicked away to the Docker page (maybe?) and that didn't load—I get an nginx error 500—so I clicked back to Main, and that also didn't load (same error). Huh??
Meanwhile, all Docker containers are running fine, and the shares and unassigned drive are operating normally. Good, of course, but even bigger "Huh?!?"
Not sure what to do next. Haven't rebooted, because all I know how to do is a hard stop, which doesn't seem smart (if I can avoid it).
Don't suppose somebody could help me get this sorted out, please?
I have same problem.
docker works etc but WEBGUI is not available "nginx error 500".
I shut down the server and restarted.
Now I cannot access webgui, nor start my discs (which are encrypted).
Any help on how to resolve this?
-
5 minutes ago, dlandon said:
Yes.
Post diagnostics for other issues.
If by diagnostics you mean "LOG" from here, these logs are empty.
Are there other diagnostics?
-
On 12/5/2020 at 11:23 AM, dlandon said:
The latest version of UD maps the remote shares to /mnt/remotes/. You are encouraged to change your Docker Container and VM mappings to the new mount point.
If you can't do that, go the UD settings and set 'Legacy Mount Point Compatibility?' to 'Yes'. Then unmount and re-mount the remote shares. There will be symlinks created at /mnt/disks/ to the remote shares mounted at /mnt/remotes/. You won't have to change any Docker Container or VM mappings.
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.
-
On 12/18/2020 at 11:49 PM, tmor2 said:
Problem with ATTACHMENTS!
I have BW with Letsencrypt. Everything works fine except attachments.
When I attach a document (e.g an image to Identity), then try to open it I get following errors:
(1) On iPhone/iPad: "Unable to download File"
(2) On Mac (with BW being standalone app): the spinning wheel appears (as if trying to download a document) - spinning wheel stays for hours. No error message.
When I go to UNRAID->appdata (share) - I can clearly see that the images I uploaded are stored in separate directory and hashed.
Someone raised similar issue on Github here and here, but I don't know how to apply solution on UNRAID with letsencrypt
Any help?
Solved.
Problem was in appdata/bitwarden/config.json file.
Second line should have started with "https" and not "http",.
-
9 hours ago, aterfax said:
You are familiar with the concept of the past I assume?
Edit: Here are the docs you need, your certificate files are not in the keys folder: https://certbot.eff.org/docs/using.html#where-are-my-certificatesThanks,
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.
-
/etc/letsencrypt/archive and /etc/letsencrypt/keys contain all previous keys and certificates, while /etc/letsencrypt/live symlinks to the latest versions.
-
In other words this statement from your refernce is simply NOT true:
- 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.
-
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.
-
On 1/27/2021 at 5:28 AM, J05u said:
I don't know what was wrong, but at the moment it's start working without vpn. I haven't done any changes at all, and file was left default like in spaceinvader guide
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).
-
6 hours ago, housewrecker said:
Changing the label is fine. I can make that update.
But looking at the XML template used by Unraid. It does not have https, it's http. I'm not sure how your situation defaulted to that.
https://github.com/Knoxie/UnraidTemplates/blob/master/gaps-unraid.xml
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.
-
9 hours ago, aterfax said:
1 - Yes these are paths.2 - I added mail.domain.com - naturally you need to have setup your CNAME / MX records and forward ports in your router/network gateway to the Poste.io server. If you wish for the web GUI of poste.io also to be accessible externally you will also need to setup the correct reverse proxy with SWAG. I don't know what you mean by .config
3 - I blanked the folder in the screen shot as I do not want to share my domain name, but yes the subfolder with your domain name / subdomain name is where the PEM files should be if you have setup SWAG correctly to get SSL certificates. If you are lacking certificates you have probably got it setup incorrectly.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
-
5 hours ago, J05u said:
as i said above, by some strange reasons it's working on my IOS devices only when i have vpn turned on, even Adguard vpn which is not changing my IP
In your UNRAID/appdata/bitwarden/config.json file, 2nd line, "domain"...does your value start with http or https?
-
1
-
-
On 1/20/2021 at 6:04 AM, J05u said:
Can't access it with my subdomain
don't know what is wrong
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).
-
1
-
Your DNS provider
-
On 1/20/2021 at 10:23 PM, DingHo said:
@tmor2 Did this fix it? I have the same CPU as you, and I'm considering to move it to my unraid tower. Any chance you could confirm if you can get HW x265 4k HDR --> 1080p SDR with tone mapping encoding to work with the iGPU? Very much appreciated.
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?
-
51 minutes ago, housewrecker said:
SSL false would mean no HTTPS. Did you have a question about that or the configuration?
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.
-
On 11/16/2020 at 7:14 PM, aterfax said:
I ended up mounting the default certificate files in the docker directly to the certificates from my letsencrypt docker:
But as I mentioned further up in this thread you can also mount .well-known folders between your Poste IO and letsencrypt docker - this will not work if your domain has HSTS turned on with redirects to HTTPS (or this was the case with the version of letsencypt in the docker a while ago as it was reported here: https://bitbucket.org/analogic/mailserver/issues/749/lets-encrypt-errors-with-caprover )
-
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
-
How did you add this:
-
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
-
On 1/3/2021 at 6:11 PM, Roxedus said:
In what context are you using letsencypt in?
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?
-
Does anyone know whether the method for making Hardware Acceleration (HWA) in UNRAID available to Plex Docker provided here, will work for any other docker container, such as Jellyfin?
In other words, if I enable Hardware Acceleration (HWA) via "/dev/dri" on Plex, can I use the same methodology to make HWA available to other dockers?
For example, (assuming all steps were followed to edit "nano" file here) to make HWA available to jellyfin/jellyfin container, can I edit the "Jellyfin" docker and add a new device, with following details (then, of course, enable HWA within Jellyfin Web GUI):
Config Type: Device
Name: /dev/dri
Value: /dev/dri
Thnks.
-
10 hours ago, Hoopster said:
You have Plex Pass and have enabled hardware acceleration in Plex server, correct? I assume so since it is mentioned in the guide. but we just need to verify this.
I use the Extra Parameters method, but, the device method should also work.
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?
-
-
21 hours ago, Dyon said:
Is one of these lines an IPv6 address instead of IPv4?
remote [MASKED VPN server address] [MASKED port]
Try deleting the line with an IPv6 address, and keep these removed;
tun-ipv6
redirect-gateway ipv6Thank 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.
-
1 hour ago, Dyon said:
Is one of these lines an IPv6 address instead of IPv4?
remote [MASKED VPN server address] [MASKED port]
Try deleting the line with an IPv6 address, and keep these removed;
tun-ipv6
redirect-gateway ipv6All IP addresses are IPv4.
-
4 minutes ago, Dyon said:
Try this removing these two lines:
tun-ipv6
redirect-gateway ipv6It didn't work.
don't know what is wrong
Help - USB dead - app/usb backups are on encrypted drive
in General Support
Posted
This process works.