mjeshurun

Hello friends, I'm trying to install qbittorent vpn, but, unfortunately, I'm getting an "unauthorized" error message when trying to open the webui. I've seen other users had this problem before, but I didn't find a written solution. I tried to completely delete the container and the appdata folder and re-installing, but nothing helps. Can someone please explain how to solve this? 🙏 Edit: Found this solution by @gregzee posted in a comment: After the "unauthorized" issue was solved I had to figure out the solution for the default "adminadmin" password not working. This comment by @nraygun explains the solution to the password: Hope this helps others in the future 🙏

OK, thanks. I will re-format the drives. Any suggestions about drive configurations and format types? I opened another thread concerning drive best practices, and I could use help to configure the system in a better way. 1. which format type is better for SSD's: btrfs or zfs? Until now I ran my system with a btrfs cache pool consisting of two SSDs, without parity and without the use of an array drive for the mover function. Instead of using array and parity drives I backed up my data to an unassigned drive using luckybackup. 2. which practice is better, using a cache pool alongside an unassigned drive for backups, without the use of array and parity drives, or using 1 SSD for the cache drive, 1 SSD for an array drive, and a third unassigned drive for backups?

Hello friends, In the last few days my SSD btrfs cache pool suffered corruption and that started to cause issues with my server. @JorgeB suggested that I re-format the cache pool and then copy back the data from backup. I have a few questions before I proceed with the re-formatting. 1. which format type is better for SSD's: btrfs or zfs? Until now I ran my system with a btrfs cache pool consisting of two SSDs, without parity and without the use of an array drive for the mover function. Instead of using array and parity drives I backed up my data to an unassigned drive using luckybackup. 2. which practice is better, using a cache pool without the use of an array drive alongside an unassigned drive, or using 1 SSD for the cache drive, 1 SSD for an array drive, and a third unassigned drive for backups?

Hi @JorgeB, I hope you don't mind if I trouble you with this issue a bit longer. It seems I still have corruptions with my cache drives pool. I've been having more unexpected issues with my system and after reading the forum I ran a filesystem check of the drives. These are the results I got: [1/7] checking root items [2/7] checking extents data extent[11303731200, 12288] bytenr mimsmatch, extent item bytenr 11303731200 file item bytenr 0 data extent[11303731200, 12288] referencer count mismatch (root 9351338399421693957 owner 16777096 offset 0) wanted 1 have 0 data extent[11303731200, 12288] referencer count mismatch (root 5 owner 9630909 offset 0) wanted 0 have 1 backpointer mismatch on [11303731200 12288] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree free space info recorded 1385 extents, counted 1397 There are still entries left in the space cache cache appears valid but isn't 965383028736 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sde1 UUID: e0192f98-c083-4849-b444-e7c7a122f3e4 found 1210729578496 bytes used, error(s) found total csum bytes: 429124228 total tree bytes: 1053720576 total fs tree bytes: 380370944 total extent tree bytes: 135462912 btree space waste bytes: 192168905 file data blocks allocated: 3048914657280 referenced 1179449688064 Are these issues that can be fixed or do I need to re-format the cache pool, as you suggested initially?

Hello Friends, I've recently had an issue with my server SSD and my docker.img got corrupted. After I deleted the old docker.img file, I re-installed all my docker apps from the previously installed templates. And now I'm able to use most apps I previously had with their previous appdata intact. Unfortunately though, I'm having a strange issue when using the NginxProxyManager container. When I set the container to use a custom network type I created, the app's webui loads, but I can't log into NPM's control dashboard. Nothing happens when I press "sign in" and I'm using the correct email/password combination. However, if I change the network type to Host, I am able to sign in using the webui into the control dashboard, but then non of my other docker apps (which I configured to work with NPM for external internet access with my domain name) are available when I try to use them the sub-domain addresses I created for them. Is this issue familiar to someone? I will appreciate any help solving this issue 🙏 Update: after disabling Unraid's Use UPnP under Management Access, I'm now able to log into the NPM dashboard when using a custom network type. However, I still can't reach any of my docker services that use the external domain addresses I defined in NPM with let's encrypt certificates.

Here is the new diagnostics file. Hope it helps shed some light on the issues I'm still having. tower-diagnostics-20240112-1828.zip

Thank you for the explanation 🙏 After renaming the old docker.img file to docker.tmp I managed to start the docker service and re-install the containers. However, I found a few more problems that don't work as they did before the cache drives "unmountable" issue. 1. I have a few docker services I configured to work with NginxProxyManager. Although I was abale to reach these services in the past, they now fail to load with my external domain address. I can reach these containers' webui using my internal server ip address, but not with my external domain address. 2. if I set NginxProxyManager to use a custom network type, it opens the webui login page, but I can't log in. I can only log in if I set NginxProxyManager network type to Host. Can that be the reason I can't reach my containers using the external domain address? 3. VM's are also not working properly, and I'm seeing this error message when trying to go to the VMs tab: "Libvirt Service failed to start". Do I also need to delete/rename the libvirt.img file?

Thank you, very much. For some unknown reason to me, today the cache drives are no longer showing the "Unmountable: Unsupported or no file system" message. I still got the "docker service failed to load" message. I renamed the old docker.img file to docker.tmp and restarted docker, and now docker loads properly, though with no containers. Is there an easy way to bring back all my containers (without needing to manually reinstall each container using the template)? Should I still format the cache drive pool even if it's mounting properly now?

OK, thanks 🙏 Sorry for the noob questions, but after backing up the cache data, how do I re-format the cache drive pool? After formatting do I just copy back all the data to the cache pool from the backup?

Can you please explain how best to backup the cache pool? And how to recreate the docker image?

Thank you very much,@JorgeBfor the quick response to my post. using the command you included does bring back the cache pool back, but it only stays detectable till the next array restart. If I restart the array another time the cache pool shows the same error message again. Also, after I use the command you mention and the cache pool is detected, I'm seeing a docker service failed to start error message.

Hello friends, I'm facing a serious issue. I upgraded my Unraid to 6.12.6 a few days ago and everything was working properly until now. Last thing I did with my system was update the mariadb docker app and then I restarted my system. I didn't add any new drives. After I restarted my system I got an error message saying the cache pool is: "Unmountable: Unsupported or no file system". From reading other posts on this matter, I added my diagnostics file. Can someone please explain what I can do to fix this? 🙏🙏 tower-diagnostics-20240111-1549.zip

Thanks for the explanation. My container is currently set to root. Is it more advisable to run the container as non-root?

My time zone is Asia/Jerusalem. I'm not sure if I'm using the container as non root. How do I check that?

Yup, I just wanted to confirm in this thread that your solution worked for me

Using the 'date' command in the container terminal I found my time zone was not set correctly. After I set the correct TZ using the following solution: Log into docker console (you will be root), and execute: su - luckybackup touch .profile echo "export TZ=America/New_York" > .profile And now the time in the email is displaying properly.

Hi all, I started using luckyBackup a few days ago and it's working great. I did notice one thing not quite right. When I set the app to send me an automated email after a scheduled backup has finished the backup time shown in the email is off by 1 hour, although the backup actually started at the right time set in the schedule. Is there a place we can set the time zone the app uses? Maybe that's the reason the time shown in the email is off by 1 hour.

Thank you very much 🙏 I wasn't aware of this padlock reordering method.

Hello friends, Is there a way to manually reorder the folders we create with this plugin? I can't find a way to do that. I know how to change the internal order of the apps within a folder, but I would like to change the order of the folders. Currently, the order is based on when the folders were chronologically created -- so that the newest folder created is on the top of the folders list, and the oldest created folder is on the bottom. If possible, would like to manually change this order. Hope someone can help 🙏

Hi @jbrodriguez, Is the Feature Request Forum down? I wanted to see what the requested features list includes, but all I see is a web page saying "Loading".

Thanks, everyone, for all your help 🙏🙏 I think I finally got Cloudflare-DDNS-config to work with no error messages. I'll keep checking the logs for the next few days, but so far it appears to be working well

I'm not entirely sure the cloudflare API is the problem. If I run oznu/cloudflare-ddns app I don't get any error messages regarding the "www" subdomain. And onzu's app also depends on the cloudflare API.

Thank you very much, @semaj4712! You were correct. 🙏🙏 As I'm trying to switch from a different cloudflare ip updater, I mistakenly assumed the zone_id meant the domains URL. Your tip helped me find the actual zone_id's. However, I'm now seeing these error messages for the sub1 "www" of both domains I'm trying to set up in the config.json file. ➕ Adding new record {'type': 'A', 'name': 'www.***********.com', 'content': '**.***.***.***', 'proxied': True, 'ttl': 300} 😡 Error sending 'POST' request to 'https://api.cloudflare.com/client/v4/zones/*****************************/dns_records': {"result":null,"success":false,"errors":[{"code":81054,"message":"A CNAME record with that host already exists. For more details, refer to \u003chttps://developers.cloudflare.com/dns/manage-dns-records/troubleshooting/records-with-same-name/\u003e."}],"messages":[]} Any ideas how to solve this?

I've double checked my zone_id and the api_token password and they are correct. Are these the correct token permissions I should set? Zone Settings:Read, Zone:Read, DNS:Edit

Hi @Kilrah, thank you for posting an example of your config file. I'm seeing the following error message repeatedly in the container's log, when I try to build my config file based on yours. Obviously, I used my own api-token and zone address. For the sake of privacy I change the actual zone address in the log error quote to "********.com". 😡 Error sending 'GET' request to 'https://api.cloudflare.com/client/v4/zones/********.com': {"result":null,"success":false,"errors":[{"code":7003,"message":"Could not route to /client/v4/zones/********.com, perhaps your object identifier is invalid?"}],"messages":[]} Do you have any idea why this error is happening?