I'm currently facing some troubles by reaching my https-endpoint for my alexa-custom-skill. My endpoint is an internal PC in my network. For reaching this webserver I use a DDNS ( . linkpc.net) for my router. The router itself has a port forwarding (443 => internal WebServer Port). That means the current architecture is:
Alexa => Router ( . linkpc.net):443 => : => RESPONSE => ROUTER => Alexa
I also created a self-signed certificate, that is placed inside a jks and loaded by my WebServer.
This solution works well, by calling the URL ( . linkpc.net/xxx/xxx) via browser. I receive a message that connection is unsecure due to an untrusted certificate (my self-signed one). But that is a normal behaviour.
I imported the self-signed certificate to "SSL certificate" via Amazon DEV Console (PEM Format).
From my point of view everything should be fine, but I get the following error by sending a request over Amazon Dev Console:
"The remote endpoint could not be called, or the response it returned was invalid."
If I'm going to copy the xml-text and insert it to JSON chapter I got:
"There was an exception during the SSL hand shake. Please check the certificate you have provided."
I also created a BreakPoint in Ecplise. It works by using Browser, but it didn't by using Dev Console. No response in the code. That means, from my personal point of view, the request is not even reaching my WebServer at all. There are three possible explanations (maybe):
1. Router provides the wrong certificate to Alexa (strange, because it should not work as a proxy and shouldn't need the self-signed certificate?)
2. Self-Signed certificate is wrong?!
3. A bug inside dev console (unlikely)
Could you please support? :-)