Jump to content

Jimmy90

Members
  • Posts

    91
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Jimmy90

  1. On 10/27/2018 at 8:15 PM, deaerator said:

    Thank you for the help.

    I had to move the keyfile temparory to that location until it was formatted and mounted.  Then I deleted and did a re-boot and everything is working correctly.

     

    You just made my day! Thanks for sharing your resolution steps! I was equally successful in that manner!

  2. Ok, well, I guess I was able to get it right after much trial and errors :(

     

    First and foremost, your library must be impeccable in terms of ID3 tagging. I've got well over 2500 tracks in mine and to be honest, i hadn't really kept it clean since my OS X Leopard days  ::) So in the end, it took a couple of hours  :-[ Pathetic....I know...

     

    Anyhow, here's what I've done. Koel is syncing fine now, just like a homemade Spotify:

    1) Used an App called TagStripper in MacOS and stripped all tags from my library (in my case, Music share). The automation process took about an hour.

    2) Installed Mp3Tag software in a WIndows VM and processed my entire collection using the Action "Filename - Tag"

    http://www.mp3tag.de/en/

    3) Then, followed this guide to reassign and embed Album Art as it should to my library: https://tinyapps.org/blog/windows/201409100700_batch_download_embed_cover_art.html

     

    I'm pooped!  :-\ But hey, its working now! Using /media in the settings.

     

    Thanks for yet another much appreciated Docker contribution Binhex!

     

    Jimmy

    Screen_Shot__1.png.ae508b1ec6553f4ad3dfdcdfea8b2db7.png

  3. So i've mapped my /media path to /mnt/user/Music but for some reason, nothing shows up in koel's library. I've tried scanning for for /media , /media/ or even media in the settings, but no joy :( 

     

    No permission issues with the Music share either, i triple checked that.

     

    Anyone? Thanks

  4. By the way, anyone getting such an error when attempting to load privoxy in the browser?

     

    Invalid header received from client.

     

    Yup :( same here for some time now. Something must've changed with the latest update....

     

    i think you guys might be misunderstanding how to use privoxy, you dont point your browser AT privoxy, you configure the browser to USE the proxy, if you just try going to http://<server ip>:8118 then yes you will receive the above message, instead you should be doing something like this (example is for chrome):-

     

    To set up or change network connections, follow these steps:

    Click the Chrome menu on the browser toolbar.

    Select Settings.

    Click Show advanced settings.

    In the "Network" section, click Change proxy settings

    Now in LAN settings enter in ip of your server and port of 8118

    Click OK and test

     

    Tested and working with the latest docker image.

     

    Thanks Binhex, I was already very familiar with that part :) But in the past, clicking on the server:8118 link would take you to the config page where you could adjust filters and such. I've been using your outstanding container since day 1 and I'm pretty sure i didn't dream this one up! :)

     

    And for the record, yes, you are absolutely correct, the proxy functions as designed though, so no worries here  8)

×
×
  • Create New...