[FrightenedRat]

Hey, I finally got this working self-hosted! - but only with a dynamic dns - it just refused point blank to accept a self-signed certificate with my public ip. Many thanks to the dev and support community who have made this possible.

But, since I've been up all night and my eyes are fried and my brain in melt down, can anyone tell me the voice command to close Alexa''s visual overlay that pops up on a fire tv with search results?

Also, whenever there's a hickup in retrieving results, the fall-over response seems to be to play recently added music - which is driving me mad because I've now heard the same podcast intro about fifty times. Is there a way to tweak this?

Thanks - oh, and Merry Christmas one and all!

 Hi... Can you give some pointers as to how you got it working self-hosted? I"m attempting to do this but all I'm getting is a 404 Not Found when I test from developer.amazon.com. I'm pretty sure I have a working web server (nginx on Ubuntu 16.04) and a working uWSGI environment as I can serve other python applications successfully (A simple Hello World app).

I've cloned the github repository into a virtualenv environment and created the kodi.config which has the internal DNS entry for the kodi box I'm trying to interact with and followed the skill setup guide. I have a letsencrypt SSL cert for the server and this presents as trusted in a browser.

I'm presuming I need to use the alexa.wsgi file to start the server under uWSGI?

Any hints/tips/pointers greatly appreciated. 

Hi, I used apache rather than nginx. For me the steps that required care or changes from the original step by step instructions for setting up apache (earlier on this thread) were:

• run   sudo apt-get install libffi-dev   before installing the extra requirements with sudo pip install -r requirements.txt
  
• the port, dns, kodi name and password now go in /var/www/html/kodi-alexa/kodi.config - I haven't made any other changes to the template kodi.config as yet.
  
• the certificate signing that ended up working for me had to have a dns rather than a public ip, and the common name had to be the skill name, with the DNS appearing in a separate DNS.1 entry - as per the instructions on Amazon's developer site.
  
• The script alias in apache's default-ssl.conf entry was  
  • WSGIScriptAlias /kodi-alexa /var/www/html/kodi-alexa/alexa.wsgi
    
• But the address I needed to give to amazon was https://mydns/kodi=alexa/ with a trailing slash - otherwise I encountered a redirect.
  • Note that browsing to the page directly with a GET rather than a POST produces a 405 method not allowed on apache.
    
  • If you are getting a 404 I would imagine there's something wrong with either your script alias or your port forwarding (though maybe it's different with nginx).
    
• In the apache default-ssl.conf file I ended up with   <VirtualHost *:443> and ServerName my.dns.org  - it hadn't seemed to like VirtualHost as my.dns.org:443, so I changed it to the star. (It's been an age since I've set up an apache web server so as you can see I've forgotten how things are usually done, and I was more interested in getting it working quickly than getting it right - I guess I'll need to revisit the apache config when I'm feeling less time pressured.
  

By the way, during testing, when I couldn't get the SSL handshake to complete using the Amazon test service and my public ip, I tried to POST using curl (and the -k option which keeps going past SSL errors). I was passing it a json file into which I'd pasted the json contents of the left hand box in Amazon's testing setup - the curl NEVER worked for me (500 error), even when Amazon's test service was finally happy. I'm not sure what was going wrong with that - was something extra needed besides the json contents? It would be nice to have an example of how to test with curl (if that's possible).

Good luck getting things working.