On 9/3/2019 at 4:30 AM, andreidelait said:

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;
        }
}

 

were you able to get this working? can you share in details what you did?

On 9/27/2019 at 8:18 AM, ProAm500 said:

were you able to get this working? can you share in details what you did?

Unfortunately not. It works just fine using port forwardiing but I could not make it work using letsencrypt reverse proxy.

I can access the interface, I can download songs but I cannot play anything. I will try again when I'll have more time but I feel like I've tried all I could find on the internet about this.

Edited September 29, 20196 yr by andreidelait

@binhex, any chance you can update this container? The latest release is 4.1.1. Thanks!

@binhex Please update this container to always download latest release of Koel. 

TIA

On 9/27/2019 at 9:33 AM, andreidelait said:

Unfortunately not. It works just fine using port forwardiing but I could not make it work using letsencrypt reverse proxy.

I can access the interface, I can download songs but I cannot play anything. I will try again when I'll have more time but I feel like I've tried all I could find on the internet about this.

 

On 9/27/2019 at 7:18 AM, ProAm500 said:

were you able to get this working? can you share in details what you did?

 

Make sure that your mounted media directory is owned by www-data. www-data should also be able to execute the files located in there.

chown www-data: /path/to/media -R && chmod 744 /path/to/media -R

 

19 hours ago, leehman said:

 

 

Make sure that your mounted media directory is owned by www-data. www-data should also be able to execute the files located in there.

chown www-data: /path/to/media -R && chmod 744 /path/to/media -R

 

www-data is not a user in that container

sh-4.4# cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/usr/bin/nologin
daemon:x:2:2:daemon:/:/usr/bin/nologin
mail:x:8:12:mail:/var/spool/mail:/usr/bin/nologin
ftp:x:14:11:ftp:/srv/ftp:/usr/bin/nologin
http:x:33:33:http:/srv/http:/usr/bin/nologin
nobody:x:99:100:nobody:/home/nobody:/bin/bash
systemd-journal-gateway:x:191:191:systemd-journal-gateway:/:/usr/bin/nologin
systemd-timesync:x:192:192:systemd-timesync:/:/usr/bin/nologin
systemd-network:x:193:193:systemd-network:/:/usr/bin/nologin
systemd-bus-proxy:x:194:194:systemd-bus-proxy:/:/usr/bin/nologin
systemd-resolve:x:195:195:systemd-resolve:/:/usr/bin/nologin
uuidd:x:68:68::/:/sbin/nologin
dbus:x:81:81::/:/sbin/nologin
systemd-coredump:x:998:998:systemd Core Dumper:/:/sbin/nologin
systemd-journal-upload:x:996:996:systemd Journal Upload:/:/sbin/nologin
systemd-journal-remote:x:997:997:systemd Journal Remote:/:/sbin/nologin
git:x:995:995:git daemon user:/:/usr/bin/git-shell

sh-4.4# chown www-data -R media
chown: invalid user: ‘www-data’

 

 

Actually I got it working but it's not user related.

I used the same config that you can find a few posts above but with a small change.

Instead of

proxy_pass http://<ip address>:<port>;

I chenged it to

proxy_pass https://<ip address>:8060;

 

Also you have to add a line in .env file inside of appdata config.  In my case it's

/mnt/user/appdata/binhex-koel/koel/config/.env

Edit this file and add a line

 

FORCE_HTTPS=true

Edited March 10, 20206 yr by andreidelait
fixed it

On 3/10/2020 at 6:00 AM, andreidelait said:

 

Actually I got it working but it's not user related.

I used the same config that you can find a few posts above but with a small change.

Instead of

proxy_pass http://<ip address>:<port>;

I chenged it to

proxy_pass https://<ip address>:8060;

 

Also you have to add a line in .env file inside of appdata config.  In my case it's

/mnt/user/appdata/binhex-koel/koel/config/.env

Edit this file and add a line

 

FORCE_HTTPS=true

IT WORKS! Thanks a lot. 

Hi @binhex can you update this container ? Thanks a lot

So, is this project dead?

Edited August 11, 20205 yr by Keek Uras
forgot to put a question with screencap

8 hours ago, Keek Uras said:

So, is this project dead?

sorry guys, i forgot to shut this thread down, sadly i dont have the time to fix the install of this every time there is an update (and yes it breaks every time!), so im bowing out of this app, i shall get the moderators to lock this thread.

@johnnie.black please can you lock this thread, as i will no longer be supporting this docker image (see post above for details).