Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


PhAzE last won the day on August 9 2017

PhAzE had the most liked content!

1 Follower


  • Gender
  • Personal Text
    It's never Lupus.

Recent Profile Visitors

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

PhAzE's Achievements

Community Regular

Community Regular (8/14)



  1. Hey Squid, i'm getting what appears to be a false positive on a file i created on my USB: /boot/config/usb-rules.cfg corrupted Your flash drive has possible corruption on /boot/config/usb-rules.cfg. This is the contents of that file (which just maps the zwave and zigbee controller from my HUSBZ-1 to static device entities on boot): SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="zwave" SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="zigbee" There doesn't appear to be any corruption in the file, i've recreated it just to be sure, so i'm thinking there is some sort of string of characters that the scan is detecting as corruption.
  2. Was there ever anything dicovered with this? Mine has done the same now since the 6.8.2 upgrade. Wouldn't reboot, then after a few tries it started but the array controls were missing from the GUI, just the powerdown and reboot buttons remained. Edit: after a third reboot, the start button returned.
  3. Hey there! I'm hoping someone can give me a hand with this. New to Nextcloud, trying to set it up using this guide: I setup MariaDB, edit the cfg file to uncomment the bind command, log into the db, create the user, db, add permissions, exit, restart the db container. I start up the nextcloud container, access the webGUI, fill it in and click finish, and it seems to just hang there for a while then i get a 504 gateway timeout. Not much data to go on from here. This is on my nginx error.log /mnt/cache/AppData/Nextcloud/log/nginx# cat error.log 2019/08/05 20:44:57 [error] 338#338: *4 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.1.x, server: _, request: "POST /index.php HTTP/2.0", upstream: "fastcgi://", host: "192.168.1.y:10002" Where 192.168.1.x is the computer i'm setting this up from, and 192.168.1.y is my NAS IP. I can't seem to figure out why a fresh install isn't working, is there a step i'm missing? I'm not even at the Letsencrypt steps yet, this is just a local setup that's failing. EDIT: I guess moving the log file off the share, and restarting the container got it going.
  4. What about if I move USB A to USB C first? That will blacklist USB A though, and I assume moving the key from USB B to USB A after would fail because of that blacklisting?
  5. Hello, I've got a quick key replacement question. USB A has a plus key registered (This usb device is better quality and tiny) USB B has a pro key registered (This usb device is old and large) USB C is new (This usb device is better quality but still large) I want to move the pro license from USB B to USB A, so I copy over the key file, reboot, go to the registration key which now detects an invalid key registration, and click replace. A new link is sent for the new key, and this should update USB A with the pro license and USB B GUID is now blacklisted from registration. Next, I move the plus key to USB C and follow the same procedure, however in the process will this blacklist USB A's GUID making the pro license i just moved there invalid?
  6. Yea, this was more to prove that I had the correct docker as the culprit. I just nuked the image and set an extra param path.
  7. Aw man, this saved me. I had a docker with a port binding issue, I guess it was filling logs constantly, but after repairing the bind problem, i didn't know what was eating up the docker image file... logs. *shakes fists into air*
  8. Guess they're totally dealing with a sev1 over there at the moment.
  9. Will this docker end up being the final one when it exits beta, or will the team make another docker for the final version?
  10. Just a quick update, unRaid 6.4 looks like it will be using nginx for the web front end over emhttp (which is a good switch IMO) but that means there is a good chance all of my plugins will not work on 6.4. I don't really have any plans on updating the plugins for 6.4 if this is the case, so I do suggest people plan on migrating to dockers sooner rather than later so you don't get stuck on 6.3 forever. Also, as of 6.4, my plugins will no longer show in the app store so new installs on 6.4 won't be possible by that method. It has been a great run for the past number of years. I just want to thank everyone for their support. It's been a great community to work with as I self taught myself so many new things during these projects and quite a fun (but time consuming) experience. I may dive into the docker side of things in the future but it seems most of the bases have already been pretty well covered there.
  11. I think the easy way would actually to just install the docker for the app, create a new host path that is the same both in the docker and on the host (matching the path to your PhAzE plugin config for that app) and start it up. That way any plugin can switch without having to edit the DB in any way. Also, set the network to 'host' and you can keep the same ports and everything without issue. You may need to map your downloads directory and media directory the same as the PhAzE plugin also on the Docker for it to start and work as is, but I am going to try to script it so it's dirt easy.
  12. Hey Everyone, sorry for the super long intermission. Certain aspects of my life have required a whole lot of attention with regards to one of my family members so I've been up to my eyeballs in events, meetings, and assessments for that. That being said, i also upgraded my phone (where i always received messages from this forum) and didn't even realize I was no longer receiving those messages. Fun times! I think for many people, especially when running Unraid 6.2 or newer, the best bet would be to start migrating over to dockers where possible. I will have a look over the next few weeks at updating some of the plugins so that they are working again, but still recommend migrating over when you get a chance. I suspect I am going to have a lot less time to work on these in the future and they are a little complicated to hand over to anyone else unless they really want to put in the effort to learn how they work.
  13. Ombi will check Plex directly to see if movies exist in your library vs PlexRequests which checks the movie manager (CP, Radarr, etc). Ombi is based on .net vs PlexRequests which is based on Meteor. Ombi has full user management and collects user info from that are friends with your account, to make login easy for them (aka use their plex credentials to log in) It started off as just a fork but has grown a lot faster than PlexRequests.
  14. otherwise run this: wget -qO /boot/config/plugins/Sonarr/Sonarr-PhAzE- this will download the file manually. then you can run the install from the web gui.
  15. Try this: Edit the sonarr.plg file in /boot/config/plugins folder. Look for the variable called appurl and its something like Change it to (replace update with download) then test the install again. Ill check for the direct download command if this doesnt work.