philchillbill wrote: 
> That would indicate that the Echo didn't see a valid audio stream at the
> address that LMS resolves to in your LAN. 
> 
> The normal 'Play' commands just instruct LMS to talk to your players and
> feed them as LMS does. The 'Stream' commands are different by necessity
> because the Echo needs to be fed with a stream *from a URL*, much like
> internet radio. LMS is told to start up a /stream.mp3 network client and
> then the Echo is pointed at that stream locally within your LAN. That
> last part must be failing due to your proxy/docker setup. The
> /stream.mp3 endpoint has to be unprotected and reachable over http
> without basic auth in your LAN for it to work. 
> 
> Can you share any details of your proxy or docker config? Any reason you
> didn't go the ngrok route? Earlier, you got a bad-SSL cert error (EPROTO
> 140716538210176:error:1408F10B:SSL routines:ssl3_get_record:wrong
> version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332) so
> it may also be that Amazon does not trust your proxy. You subsequently
> re-linked the skill without a port number in the https URL which
> silenced the error, but Amazon may still have issues with your proxy.
> Amazon has whitelisted ngrok which is why people who go that route never
> have issues like this.

I've returned to the UK and now have a couple of Echo Show 15s at home
and so have tried this again. I set up a new DNS cname and let my nginx
docker container get the Lets Encrypt cert for it. Player control now
works but streaming does not. I have also set up an nginx proxy for HTTP
to /stream.mp3 so it doesn't require SSL. My LMS is password protected
hpwever and /stream.mp3 expects a login as does the rest of the server.
Testing with curl (and not cached broswer sessions) proves this to me.

Can Media Server LAN access to /stream.mp3 work with security enabled on
the server?

For reference, the nginx config is below:


Code:
--------------------
    
  server {
  listen 80;
  
  server_name lms.example.com;
  
  location /stream.mp3 {
  proxy_pass http://ubuntu:9000/stream.mp3;
  }
  }
  
  server {
  listen 443 ssl;
  
  # Domain names this server should respond to.
  server_name lms.example.com;
  
  # Load the certificate files.
  ssl_certificate         /etc/letsencrypt/live/lms.example.com/fullchain.pem;
  ssl_certificate_key     /etc/letsencrypt/live/lms.example.com/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/lms.example.com/chain.pem;
  
  # Load the Diffie-Hellman parameter.
  ssl_dhparam /etc/letsencrypt/dhparams/dhparam.pem;
  
  location / {
  proxy_pass http://ubuntu:9000/;
  }
  }
  
--------------------


------------------------------------------------------------------------
Peter Galbavy's Profile: http://forums.slimdevices.com/member.php?userid=32718
View this thread: http://forums.slimdevices.com/showthread.php?t=111016

_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to