This is very strange.
I have an Alexa custom skill which controls a back in service (emby media server)
I proxy emby through caddy, which is set up though a domain and uses https.
From what I gather, information travels back and forth through caddy’s websocket to embys websockets, to my custom skill.
It works wonderfully for json information. Full control of emby, and string data moves freely between the services.
One of the options for Alexa custom skills is the ability to create card data which gets sent to your various echo screen devices in your home.
Again, the string information works flawless, but image data does something different.
When Alexa contacts my domain for information and it gets routed through caddy, the only way to attach an image to the card is to use the subnet address (example 192.168.2.126). This is the only way the image seems to be available.
This causes an issue because amazon wants a TLS enabled endpoint for image aquisition, and my subnet address isn’t https.
It just won’t work through the proxy set up in caddy, so long as the devices are in the same subnet as the server hosting the service.
What is the issue? Is there a name for this type of behaviour in servers?
It is like trying to contact your domain from inside the host network… That won’t work. It seems like the same thing is happening here.
It’s hard to Google possible fixes because I’m not exactly sure what the problem is called… Because I’m so new to this sort of thing.
Any possible information which would help my learning curve would be much appreciated.
Thank you in advance.