[Soulseek Dockers]

On 7/10/2018 at 9:35 PM, realies said:

@ridge, feel free to modify this, ssl.conf and proxy.conf are part of linuxserver.io's letsencrypt nginx server, but it should run fine without them, the key thing is the /websockify connection upgrade.

 

upstream soulseek {
        server 192.168.1.100:6080;
}

server {
        server_name _;
        listen 80;
        return 301 https://$host$request_uri;
}

server {
    server_name _;
    listen 443 ssl;

    access_log /config/log/nginx/soulseek_access.log;
    error_log /config/log/nginx/soulseek_error.log;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        proxy_pass http://soulseek/;
    }

    location /websockify {
        include /config/nginx/proxy.conf;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_pass http://soulseek/;
    }
}

 

 

Hey there, Thanks for this container @realies, it works perfectly.

 

I have a question as i don't succes to put the reverse proxy on this container with linuxserver/letsencrypt docker. In this soulseek.conf file, I just change the  server line to put my local IP:6080 on wich soulseek is running. I replace the 2 "_" after the server name to put my soulseek.domain.com .

I also add the soulseek subdomain in the environment variable of letsencrypt and renewed my certificate. But I just reach the letsencrypt index maintenance page and i cannot access soulseek from the outside.

 

What am I doing wrong ? (I have other subdomains that works, the https redirection works with the soulseek subdomain, it's been two days and i can't figure what's the problem...)

Thanks

 

Resolved : I finally found that my error came from the soulseek.conf file that has to be named like that => sousleek.subdomain.conf 😛 newbie error i supose... thanks again for the plugin !