So, apparently the noob is strong with me...

 

I got the docker installed and pointed it to my music and then loaded the web UI no problem.

Logged in with supplied credentials ([email protected], admin) and went to settings to point it at my music directory and it just keeps spitting error at me saying that the location is not valid.

 

What am I doing wrong?

 

I copied the exact install directory (/mnt/user/Music/) and no joy.

Also tried //Tower/mnt/user/music, same error

Tried /music

Tried /music/ etc

It must be something simple that I am just not doing properly. Any help would be appreciated.

 

Thanks in advance and I look forward to getting this working!

 

you need to read my FAQ on docker volume mappings really as its going to help you out in the long run, here Q4:- http://lime-technology.com/forum/index.php?topic=45811.msg437673#msg437673

 

but the cheat sheet answer is set it to "/media" and then scan

Yeah I finally got it. Apparently my brain was on autopilot and comprehension was made of fail. I kept typing /music instead of /media. oops!

 

So, that being said, It began the scan, and asked for patience, this went for about 10min and then it gave an unknown error warning pop up.

Tried to run it again and after 30sec I get the same unknown error again.

 

Any ideas?

 

Yeah I finally got it. Apparently my brain was on autopilot and comprehension was made of fail. I kept typing /music instead of /media. oops!

 

So, that being said, It began the scan, and asked for patience, this went for about 10min and then it gave an unknown error warning pop up.

Tried to run it again and after 30sec I get the same unknown error again.

 

Any ideas?

The previous guy had permissions issues which were causing this, although it can be any number of problems but worth a look.

 

Sent from my SM-G900F using Tapatalk

 

 

 

This looks to be a very cool little service. I have it installed and I am getting the "Uknown Error" issue when scanning in my music. 

 

I did have some permission issues but think I have sorted them so that nobody/user are set and directories are 777 and files are 644.

 

I have scanned in one folder (and that works fine).

 

Then scanned in a few more and they work fine. Scanned my compilations (as that is a bit messy) but it worked fine.

 

Looked in a few directories to see if I had any weird audio formats or files. I had a few and scanned those folders and they all worked too.

 

Saw some "desktop,ini" files and made sure they were all deleted. 

 

There is clearly something wrong with a file or permission (as I get further and further doing the above). 

 

Is there an easy way to see what directory or file is causing the issue? I do not see anything in the log in the unRAID console. 

 

Many thanks!

 

FIX: This was related to issue #572 in Koel's GitHub. Just need to create the "covers" folder in public/images

 

Edited April 15, 20179 yr by TexasDave

I have this error when i want to install koel docker

 

Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /opt/koel/node_modules/express/node_modules/debug/node.js: no space left on device

 

What should I do?

 

Thanks.

On 17/04/2017 at 7:34 AM, publicENEMY said:

I have this error when i want to install koel docker

 

Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /opt/koel/node_modules/express/node_modules/debug/node.js: no space left on device

 

What should I do?

 

Thanks.

 

sounds like your docker image file is full, go to unraid webui, dashboard tab and check the docker image usage (near the bottom on the left), if its 100% then you either need to figure out whats filling your docker image file up, or extend the size.

On 4/20/2017 at 0:55 AM, binhex said:

 

sounds like your docker image file is full, go to unraid webui, dashboard tab and check the docker image usage (near the bottom on the left), if its 100% then you either need to figure out whats filling your docker image file up, or extend the size.

You were right. Removing some of unused docker fixed the problem.

After that, Koel works flawlessly.

Thanks.

Hey I just wanted to say awesome job on this. I was one of the uses asking someone to create it but I never had luck with it. I even trying creating my own docker at one point. I gave up early on even after you create this one.

 

I decided to give it another try. Increased the memory and timeout and it error scanning finally went away. It still took a few scans and a reboots until all my music was there but I believe it see it all now. I still have some cover art issues but I can live with that. I am 100000% percent farther then I was last years.

 

Thanks again!

Hi, 

Installs the docker, but can't login with admin@example, admin...???

 

/Lappen

29 minutes ago, Lappen said:

Hi, 

Installs the docker, but can't login with admin@example, admin...???

 

/Lappen

 

im afraid the latest docker image is currently screwed, i havent had chance to fix it up, you can roll back to the previous version if you want to get it going again, follow instructions below Q11:-

 

 

Are you going to keep working on this @binhex?  Looks good!

On 25/01/2018 at 7:17 AM, GreenEyedMonster said:

Are you going to keep working on this @binhex?  Looks good!

 

im on the case, changes in the way you feed in initial setup params is the issue, i will post here when i think its fit for consumption again.

15 hours ago, binhex said:

 

im on the case, changes in the way you feed in initial setup params is the issue, i will post here when i think its fit for consumption again.

 

Thanks man you rock!!!

Alright, its now fixed up and seems to work for me, give the latest image a spin

Didn't work.  @binhex

Edited February 22, 20188 yr by GreenEyedMonster

8 hours ago, GreenEyedMonster said:

Didn't work.  @binhex

 

try stopping the container then delete everything in /config for this container, then start it again, that should get it running, obviously you will need to rescan your library.

On 2/22/2018 at 5:13 AM, binhex said:

 

try stopping the container then delete everything in /config for this container, then start it again, that should get it running, obviously you will need to rescan your library.

Worked!!  Thanks Binhex!!

I'm having issues playing FLAC files. MP3 files play just fine.  Please let me know what would help you solve this issue. @binhex

 

Thank you.

Edited June 19, 20188 yr by grizzle33

Has anyone gotten the Last.fm integration working? I created an API key and set the variables (https://koel.phanan.net/docs/#/3rd-party) however the Koel profile page still says:

 

Last.fm Integration

This installation of Koel has no Last.fm integration. Visit Koel’s Wiki for a quick how-to.

 

Any ideas?

So after unsuccessfully trying this image, I spent quite a while tonight setting up a debian VM with koel from scratch. It was incredibly difficult to do, and I'm no novice when it comes to programming or webservers. I believe the missing component in this project was ffmpeg - my entire collection is FLAC, and it needs to be transcoded when played in the browser. Would it be possible to include that?

6 hours ago, falcor said:

So after unsuccessfully trying this image, I spent quite a while tonight setting up a debian VM with koel from scratch. It was incredibly difficult to do, and I'm no novice when it comes to programming or webservers. I believe the missing component in this project was ffmpeg - my entire collection is FLAC, and it needs to be transcoded when played in the browser. Would it be possible to include that?

i can include it if it definitely fixes your issue, but i would like to have confidence it does before pressing the button, can you try this first:-

 

open console for this container and then execute:-

pacman -S ffmpeg --noconfirm

once its installed then try flac transcoding again, if it fixes it then excellent, let me know and i can include it

Unfortunately it's still refusing to play most of my collection. I'm going to try out FunkWhale instead, but thanks for the help!

1 hour ago, falcor said:

Unfortunately it's still refusing to play most of my collection. I'm going to try out FunkWhale instead, but thanks for the help!

if i were you i would switch to airsonic, its fast, stable and imho beats the pants off koel in pretty much every way.

Hi,

 

Did someone managed to reverse proxy koel as a subdomain with letsencript? All I get it's a blank page.

I've also tried the nginex config found in this article

https://blog.qoba.lt/koel_with_docker.html

 

 

UPDATE:

Now I can see the interface but I can't play any song. If I use it with local IP everything works fine.

Here's the config

server {

  listen 443 ssl;

  root /config/www;
  index index.html index.htm index.php;

  server_name <subdomain>;

  include /config/nginx/ssl.conf;

  client_max_body_size 0;


location / {

#       include /config/nginx/proxy.conf;
        proxy_pass http://<ip address>:<port>;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header X-Forwarded-Host $server_name;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto https;
        sub_filter "http://<web address>" "https://<web address>";
        sub_filter_once off;
        add_header Front-End-Https on;
        }
}

 

Edited September 3, 20196 yr by andreidelait
some progress made

Still somewhat of a unraid n00b so hopefully someone can help me out. I'm trying to accessing koel outside of my local network via domain and subdomain that i have created . I have success using spaceinvaders instructions for emby, sonarr, etc using the templates and doing the necessary edits that have been included in the proxy-conf folder for letsencrypt. There isn't a template for koel and im having some issues getting access from outside my network. Can you guys take a look  and see what i might have wrong in my config? I can "connect", but its unsecure and only a blank white page shows up. ( i currently have the koel docker shutdown until I can figure out whats going wrong ). 

server {
    listen 80;
    server_name <subdomain>.*;
    return 301 https://$host$request_uri;
}


server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name <subdomain>.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_koel binhex-koel;
        proxy_pass http://$upstream_koel:8050;
        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

 

 

 

Edited September 27, 20196 yr by ProAm500
edited