IronBeardKnight

Members
  • Posts

    27
  • Joined

  • Last visited

Recent Profile Visitors

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

IronBeardKnight's Achievements

Newbie

Newbie (1/14)

4

Reputation

  1. I have fixed this issue for anyone wanting to know what the problem is step 1: Grafana Step 2: Grafana make sure this is your local ip if your not exposing unraid or grafana to the internet and your keeping it local. Step 3: Grafana Confirm you have the correct Encryption method selected or if your running non engcryption and apply. Do this for every graph that uses the Unraid-API
  2. Still not able to see icons. Everything else is working just not the icons. Linking back to that post on the first form page does nothing it does not explain whats going on or perhaps how to fix it.
  3. I believe from memory I just wiped the kvm image from unraid but left the vdisk in tact then recreated the kvm and pointed it to the old disk and it worked.
  4. Same for me the server now has to be fully rebooted just to bring kvm back up. did you guys get any updates on this?
  5. tried editing in GEN_SSL but it just completely breaks the container.
  6. man I'm having so much trouble with this container .env trick then get chown error for it in the setup page, so chow whole app directory as the ,env does not exist anymore. Wooo hoo one sep further. then straight up after submit on setup page straight up 500 error. and so many errors in the logs child 37 said into stderr: "src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure)) #36 etc etc. would be so good if this worked properly. Not sure why this container self generates ssl cert through lets encrypt but most people running the container will be using reverse proxies anyway.
  7. Currently Invoiceninja unraid container is not working at all and no instructions to navigate the errors. It appears your docker container is broken. Not only do you have to run php artisan migrate but after you get the db and everything setup for this you run into the below errors along with many more of the same type. [15-Mar-2021 14:19:32] WARNING: [pool www] child 31 said into stderr: "[2021-03-15 04:19:32] production.ERROR: ***RuntimeException*** [0] : /var/www/app/vendor/turbo124/framework/src/Illuminate/Encryption/Encrypter.php [Line 43] => The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths. {"context":"PHP","user_id":0,"account_id":0,"user_name":"","method":"GET","user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.86 Safari/537.36","locale":"en","ip":"192.168.1.14","count":1,"is_console":"no","is_api":"no","db_server":"mysql","url":"/"} []" [15-Mar-2021 14:19:32] WARNING: [pool www] child 31 said into stderr: "[2021-03-15 04:19:32] production.ERROR: [stacktrace] 2021-03-15 04:19:32 The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths.: #0 /var/www/app/vendor/turbo124/framework/src/Illuminate/Encryption/EncryptionServiceProvider.php(28): Illuminate\Encryption\Encrypter->__construct('7kg2Ca9E8BTaSa8...', 'AES-256-CBC') #1 /var/www/app/vendor/turbo124/framework/src/Illuminate/Container/Container.php(749): Illuminate\Encryption\EncryptionServiceProvider->Illuminate\Encryption\{closure}(Object(Illuminate\Foundation\Application), Array) #2 /var/www/app/vendor/turbo124/framework/src/Illuminate/Container/Container.php(631): Illuminate\Container\Container->build(Object(Closure)) #3 /var/www/app/vendor/turbo124/framework/src/Illuminate/Container/Container.php(586): Illuminate\Container\Container->resolve('encrypter', Array) #4 /var/www/app/vendor/turbo124/framework/src/Illuminate/Foundation/Application.php(732): Illu...
  8. Hi @ich777, Thank you first of all for all your application containers. RapidPhotoDownloader seems to be broken. I have tried wiping container completely and then redownloading with both the latest url (version 24) and also the default url that you have published the docker with being (version 17) and both seem to be getting the below error over and over again.
  9. very interesting. I'm wondering if this is an older version thing or something because at default compression levels pigz is better for speed of both compression and massively faster at decompression however actual size is not so good. I do believe that this plugin could use some work on the descriptions of each setting for example doing away with gzip and just referencing pigz to avoid confusion as to wether its using multithread or not. This is an awesome comparison of may different compression methods. Compression Comparison just scroll down.
  10. hmm if its munching cpu hard is it trying to move something that is actually running like vm's or docker containers or anything. cpu would spike hard if you where to try move something that is actively processing data. you may also have downloads trying to feed your cache i you have set it up that way and when the mover runs its trying to move active files ? What are your share settings per share that use the cache? There are many possibilities here and given to the amount of variables that can be associated with using cache and thus the mover its just a process of narrowing things down one at a time. Its possible if you have an overclock as well that bclk if modified is too high causing further instability on other system device e,g sata/sas drives, pcie lanes which could have adverse affects. I know its a pain but stock everything except your raid itself and go one by one if all else fails. I'm not having a go just trying to be helpful as much as I can , Please let us know how you go.
  11. Hey Mate, yeah just suggestions I think option one would also be the easiest as well. The second option was is such a rare case situation that it can be stored in the archive for later use if you ever need or there is demand for it later maybe. Oh also I think the spelling mistake may still be there fyi as I could see it even after updating the plugin. Hint For The Masses: We need keep in mind that exclusion file types or locations should always come before criteria to move based on ages/ last accessed/ space or what ever else as exclusions are for sub-directories and/or files that need to stay in cache no matter what other options you have selected. Personally these new features have sped up my nextcloud instance alone exponentially and I'm looking to do some testing with game load time as well in future. Thank you again to @hugenbdd for doing all the ground work.
  12. A Small Guide For those that want to use the new features but are a little lost or perhaps this will save you some time. Open Unraid CMD. cd /boot/config/plugins/ca.mover.tuning sudo nano skiplist.txt In the nano editor you can list your locations to skip like the following: Ctl + o Ctl +x Note: The list of locations may include or not include /mnt/cache/ as this is already catered for withing the mover script Find Specific files of a name or kind you may find for example all .png in a location and then put them in your exclusion list incase they are mixed in with other files and such example below. find "/mnt/cache" -type f \( -name "*.png"\) -print Open CA Mover Tuning GUI In CA Mover Tuning Plugin Set the location of your skiplist.txt as below File list path: /boot/config/plugins/ca.mover.tuning/skiplist.txt
  13. Hello @guythnick and @hugenbdd I also though of this but I tough one thing at a time. Option 1 This is the change I was thinking removing yes and adding in bigger and smaller as the on options which change the functionality of the size in the next line. Option 2 The option that has just been introduced to filter files on extension would also solve this same issue if it was ONLY used in relation to your locations you stipulate in the path skiplist.txt file, however this is not the case as the extension option covers all files with specified extension across the ENTIRE cache. On a side note: @hugenbdd I also tested your sparseness option using ( Create Sparse File ) however it did not seem to pick it up for movement, however I may be testing incorrectly I'm not sure.
  14. You should not have to rename it. The strings in the file should be being passed through this plugin with any paths being encased in double quote. @hugenbdd I think I also mentioned this to you in my notes from first testings with you as well, All file Paths need to be encased in "" otherwise the script language thinks its a new parameter or command. Also form one terrible speller too probably someone how made a mistake, you have a spelling error I'm setting up for some testing tonight.