binhex

Community Developer
  • Posts

    7879
  • Joined

  • Last visited

  • Days Won

    37

binhex last won the day on December 20 2023

binhex had the most liked content!

Retained

  • Member Title
    I got 99 problems, and unRAID ain't 1.

Converted

  • Gender
    Undisclosed
  • URL
    https://tinyurl.com/yy9adu7a
  • Personal Text
    Addicted to the internet

Recent Profile Visitors

46547 profile views

binhex's Achievements

Mentor

Mentor (12/14)

1.4k

Reputation

  1. After update I am unable to change anything in my port mappings. Tried multiple different network options. Please Help!

     

    Update: I set it to custom br0 and am able to access now. But will not run through bridged.

  2. it will depend on how large your database is as to how long it will take, give it an hour, if it hasnt progressed then restart the container and hope for the best.
  3. you should of left it to complete, if you shutdown the container part way through then you will bugger up your database. if you now do have a corrupt database (likely if you did the above) then follow Q4 and Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  4. 2 things to check:- 1. go to unraid docker web ui, left click sonarr and select 'edit' then top right click on 'basic view' toggle to turn it on to 'advanced view', then check the 'repository' it should be set to 'binhex/arch-sonarr' if it has a colon and then some value then you are hard set to a particular tagged image, remove the colon and the value after it. 2. go to unraid docker web ui, click on top right click on 'basic view' toggle to turn it on to 'advanced view' then click on 'force update' link. this should sort you out, and to answer your question, no i would not expect an old CA plugin to block updates to docker images.
  5. that is a very odd version! same as the other guy, i have never produced that version, or at least i have no image tagged with that version, the current latest version is Sonarr 4.0.2.1183:-
  6. I have never released Sonarr version 3.0.4.1126. you sure about that?
  7. ok so walk me through the steps you did in the web ui to make it error, also you are up to date right?, please ensure you have done a 'force update' edit - using cloudflare by any chance?
  8. im using this image myself and search works with no issue, i can also add a series and see details about the new series, what am i missing here?
  9. ok then im out of ideas, all i can say is i use this image and it works for me *shrug*.
  10. it looks like this maybe related to out of date mono, so i have kicked off the build again, please pull down latest in around 30 mins from now and report back.
  11. Correct Sent from my 22021211RG using Tapatalk
  12. Yeah, this is the problem with bundling more and more stuff into the image, as soon as anything goes out of date people want the image rebuilding, so I'm loathed to include stuff that changes frequently, especially stuff that is not necessary, sorry but its a no to including it.
  13. check its not database corruption (common), Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  14. OK thanks for that, so it looks like the package 'kio' includes sftp and it looks like the package version has now bumped up to 'kio5' which once included in the build meant that sftp was available again (amongst other additional functionality). Hey no worries, everyone has stuff going on in their lives, i hope you are ok.
  15. i fixed up the broken github action for the base (it was on my todo list) which then kicked off the intermediate image builds, once done then i re-crated the krusader image, and due to the fact there were no updates as the base image is now up to date, the size of the image was dramatically reduced. from now on we should be back to more frequent automated base image builds, which should help alleviate any large increases in image size due to update churn.