Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

12 Good

About IanB

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. >Better don't support them and give the user a big red warning to set a password!!! While I think it's a terrible idea to run your server without a root password, I didn't think it was for me to try and force the user into setting one. The bug report came in and I wanted to allow the user to still access their server. That said, a red warning message to remind the user how dangerous it is might be nice. Pester them into better practices
  2. Great, thanks! I pushed a few updates to the store over the weekend to fix the reported connection issues... ### 1.4 ### - Fix issue preventing dashboard loading when no cache was being used. - Support servers where no password is set. ### 1.3 ### - Fix minor clipping of cards - Fix crash when IP/host included additional whitespace.
  3. @MMW - Thanks for the logs, it looks to be failing to either retrieve the Array information or the Cache info. Do you have an array configured and not using any cache drives?
  4. I've pushed a fix (v1.3) to Google Play to fix the crash when the IP address includes a space either at the beginning or the end. I'll probably need to do some additional validation of the input (rather than crashing) but wanted to get this fix out ASAP for you. I'm not sure how long Google is taking now, but hopefully you'll receive the update soon.
  5. >With just the server ip in a new connection it still just crashes. @MMW Sorry about this. Are you able to send me a bug report from the app? If you're at the Server List page, in the top right the "..." option includes an option "Send Bug Report". This will let you send yourself an email with app logs, which you could upload here for me to take a peak. EDIT: I just checked the crash reporting and see a repeated attempt to add an IP address that includes a trailing space. Looks like i'm not trimming what is entered (sorry). I'll get that fixed ASAP but if that is you, hopefully you can just delete the space character at the end to let you proceed.
  6. Thanks @HynesJeff, I really appreciate the support! I don't suppose you could leave an (honest) review via Google Play. I'm hoping that with more feedback, the discoverability of the app will improve via Search. As for your requests, i'd love to implement that (given time), the problem is that with the lack of a real (stable) Unraid API, the more features I add the risk I am at new updates completely breaking everything and needing to rewrite, while still trying to support older server versions - so a headache. It has been suggested that an API is on the way though, and once released I would hope to be able to quickly switch over to it unlocking the potential of additional features like the ones you suggested. My short term plan is to continue working on the core features and the application host itself to make the experience as good as possible, so it's ready for the API to quickly add lots of great new features.
  7. And another quick update to resolve an important DNS rebinding issue, along with a small bucketful of fixes. I also gave larger tablets some love with some small optimisations for their screen size. The update should hopefully be available via Google Play soon: ### 1.2 ### - [NEW] Optimised tablet layout support - Display disk state correctly (spun up or down) - Fix issue with self-signed certificates failing DNS rebinding protection - Fix crash when backgrounding app after connecting to server - Fix pie chart when displaying more than 12 shares - Sort disks so that Parity drives are always first
  8. Just pushed a new build to Google Play after some great feedback from testers. It should hopefully already be available. ### 1.1 ### - [NEW] Support for self-signed certificates - [NEW] Improved Add Server screen - [NEW] Allow offline servers to be added - Add message to server list when no servers added - Fix crash if trying to add server before providing any host information - Fix share information populating wrongly - Update persisted server information when connecting - Fix crash restoring app - Fix timeout when calculating sizes of large shares
  9. Hey 👋 This started off as a bit of a hobby project that slowly become something that I thought could be useful to others. It was an exercise for me in writing a new app from scratch and the different choices I would make, compared to having to constantly iterate on an existing (large) code base. After sharing this with some of the community in the unofficial discord channel, I was encouraged to get it into a state where it makes sense for others to use. https://play.google.com/store/apps/details?id=uk.liquidsoftware.companion I've already received some great feedback as well as a number of issues and requests for new features, that I hope to add soon. I hope others will find this as useful as I do in managing your UNRAID servers. Enjoy
  10. I've been able to actually update the app and have it mostly working. There is still some issues I need to iron out, as well as potentially some UX nits that I would clean up first if I was to launch this. Is there anyone at Unraid that I can (or should?) talk too regarding this app? I'm still in two minds what to do with it (it was a hobby project), but it could provide some value to users. I would be happy to share details of the app, a video or even an APK for feedback/thoughts from the team. @Squid Sorry for the ping, but do you know who would be best to contact and how?
  11. Sorry, I haven’t had time in a while. Due to no official API, the Unraid updates have broken what I previously had working. Hopefully I’ll have time soon but my job keeps me busy 😅
  12. Does anyone know if Unraid do any request limiting for clients? I've been making good progress with my application but finding that when it initially loads, it can be pretty slow. Debugging it shows that there is an unexpected delay when making a number of requests to the server. If I delay (myself) between the requests, the response are very fast... Sequential ========== [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 2.332s Sequential (Reverse Order) ============================== [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 2.228s Sequential (Delay between requests) =================================== [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 0.267s [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 0.143s Individual ========== [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 0.165s ... [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 0.306s Any help would be appreciated
  13. Sorry @Squid, not sure I follow. I'm basically trying to programmatically determine the same details presented here by the Web interface: Thanks in advance
  14. @Squid Don't suppose you know an easy way to obtain the `Uptime` from the server? I had hoped to also find it in the same var.ini file, but doesn't seem to be present...
  15. Thanks @Squid! I totally missed that, accessible via "/state/var.ini".