tmor2

Members
  • Content Count

    52
  • Joined

Community Reputation

3 Neutral

About tmor2

  • Rank
    Newbie

Recent Profile Visitors

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

  1. SOLVED USB stick was dead. Had to reinstall UNRAID OS on a new USB stick. Luckily I had configuration saved.
  2. 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_Di
  3. {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:
  4. 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. If by diagnostics you mean "LOG" from here, these logs are empty. Are there other diagnostics?
  6. 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 moun
  7. Solved. Problem was in appdata/bitwarden/config.json file. Second line should have started with "https" and not "http",.
  8. 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 fold
  9. 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).
  10. 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.
  11. 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 b
  12. In your UNRAID/appdata/bitwarden/config.json file, 2nd line, "domain"...does your value start with http or https?
  13. 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 na