Jump to content

eafx

Members
  • Content Count

    37
  • Joined

  • Last visited

Posts posted by eafx


  1. 32 minutes ago, Squid said:

    The update on the context menu should be there when on the docker page.  It's just not appearing correctly on the dashboard page.    (Or put another way, the dashboard's context menu would never allow you to update an app whereas the docker page would via the context menu)

    Not bothered about the update not showing on the context menu. It's just if you're using a private repo, it will always show there's an update available for that container on the dashboard (i.e. the container name is in blue text) even though it's already up to date. This behaviour was fixed in 6.8.1 but now it's back with 6.8.3


  2. Upgraded from 6.8.2 without any issues.

     

    Noticed one thing, the following change was introduced in 6.8.1, has this been removed in 6.8.3? 

     

    image.png.f05c34413388677453d7362d9d5f02a6.png

     

    I've got a private docker repo, which is now showing as there's an update available even if I try re-pulling the image. Think the above change in 6.8.1 fixed it for me but now it's back.

     

    Edit: when I say it's showing as update available, I mean container name is in blue but It doesn't give me an option to update the container on right-click.

     

     


  3. 3 hours ago, FoxxMD said:

    Fork was a poor choice of words but you know what I mean. If the way statping is staged in the author's dockerfile changes in a way that is incompatible with what you have done (new volumes? exposes new ports? requires changed/new dependencies?) then you're a link in the chain that needs to respond before updates to containers on unraid aren't broken. Are you volunteering to take on that responsibility?

     

    I will make a PR to the author with your changes to see if there is a compromise to be had first.

    Official image builds the app package from source, I'm grabbing their GH releases.

    I'm using my own alpine image as the base image of this container, which is basically a fork of lsio's alpine-base, that has s6-overlay installed (used for setting PUID/GUID and running service scripts).

     

    TBH I don't see the point of merging this with the official image. I would suggest you open up an issue on their GH requesting to add support for PUID/GUID, let's see what they say.


  4. 17 minutes ago, FoxxMD said:

    This is awesome! Could I convince you to PR your changes to the original repository though? Or I can do it. I'd rather not have to use a fork if possible, for simplicity's sake.

    It's not a fork and a different approach to the official one, so don't think there's a chance it will be merged.


  5. 28 minutes ago, Skitals said:

    It's definitely hitting the character limit for the GET request. I am changing it to a POST request.

     

    Edit: Update should be live!

    Works as expected now :) thanks!

     

    If I want to include my theme with the plugin, does my theme need to use the plugin variables or can I have it set entirely within custom styling?


  6. 1 minute ago, Skitals said:

    Can you save any changes, or only when trying to use custom variables? If you add just a few letters and hit apply, does it save? It's possible what you are inputting has special characters that are getting misinterpreted when the textarea is passed to the script.

    Happens only when using my own custom variables, no issues saving random text or css otherwise.


  7. @Skitals I'm trying to use my own custom variables for my theme in 'custom styling (advanced)' , so whenever I try to save my css with the :root { } block it won't save it, to get it to work I have to either get rid of root block or manually edit the theme's css file and then it will show up fine on the plugin but it won't allow me to edit & save it from the plugin.

     

    Any idea what's going on here?


  8. Think I'm having the same issue, updated to the latest beta from 6.8.0-rc1 almost 17hrs back and had no issues after the initial reboot, tried rebooting the server few mins back and now can't back into the GUI, not getting a ping back, I can log into the terminal via ipmi but the IPv4 address has changed to 169.254.xxx.xx range, sounds like the exact issue described here.

     

    Tried manually copying over the bz files from /boot/previous folder but it's still the same.

     

     

    titan-diagnostics-20191019-0115.zip


  9. 31 minutes ago, AnnabellaRenee87 said:

    That fixed it but I don't feel great leaving it like that, Guess there is an issue with the current version of ruTorrent/rTorrent that doesn't like being proxyed through a DNS resolver like Cloudflair.

    Yea looks like, I've rolled back to 1.1.r38.gd52abd2-1-05, the last working version with Cloudflare.


  10. On 4/18/2019 at 12:17 AM, AnnabellaRenee87 said:

    So I use the letsencrypt plugin from Linux Server.

    For some reason if I access my HTTPS ruTorrent page now it just sits at the Loading Screen with a spinner for like 5 minutes then finally loads.

    If I go to the local address:port then it loads fine.

    This just started within the last 24 hours, I haven't changed anything.

     

    I tried to remove the docker and re-add it, change settings on Lets Encrypt and even changed the TLS version with Cloud Flair, I'm stumped.

     

     

    EDIT;

    Seen this in the log for the Docker.

    2019/04/17 19:08:51 [error] 893#893: *54 open() "/usr/share/webapps/rutorrent/favicon.ico" failed (2: No such file or directory), client: 172.17.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "blah blah, my url:443", referrer: "blah blah, my url/plugins/httprpc/action.php"

     

    EDIT2;

    Copied the file from the images folder in to that directory and that error went away but the site is still sitting at loading forever.

     

    EDIT3........;

    The error is there again.......

    I'm having the exact same issue, since yesterday, it was running fine for over a year now without any issues 😐

    Edit 1: Do you use Cloudflare? I just turned off orange cloud on my rutorrent subdomain and it's working now, hmm..