It is very strange… machinesaver.io and www.machinesaver.io (which are at the same document root) both work with the non-self-signed wildcard certificate if I add them on losant.
When using the same non-self-signed-wildcard certificate for app.machinesaver.io and www.app.machinesaver.io (which are at a different document root from the aforementioned subdomains) the certificate shows as not valid when I put it in on Losant. When I use the self-signed-certificate on these two, Losant accepts the certificate but it shows the unsecured error to my users. Do you think that the document root might have something to do with the certificates working?
I am out of my element on this… I need to see our custom domain and to have customers not see a security warning from their browser when they try to access the application.
Can you please read the following response from our domain name host and give me your thoughts?
This image was part of the email but didn’t render when I copied it:
Since your losant account is not our server the SSL certificate won't work.
So I have updated the DNS records for [app.machinesaver.io](http://app.machinesaver.io) and pointed it to
our server instead. Now the SSL certificate works and when someone visits
[app.machinesaver.io](http://app.machinesaver.io) I ***redirect*** them to this URL
Try these links:
This is the prefered URL to use for your clients:
This is a workaround of course. The validation setting on *.[onlosant.com](http://onlosant.com)
has a problem with our SSL and rejects it. So the only way we can solve this
is to have the DNS pointed at our server, validate the SSL and then we redirect
it to *.[onlosant.com](http://onlosant.com).
Let me know if this solves the problem. If not then we have to ask if ****.[onlosant.com](http://onlosant.com)***
has a solution for SSL on their server. By the way I can help with that as well.
Let me know what you think. Thanks.
Unfortunately, his redirect defeats the purpose of the custom domain in the first place… so this solution doesn’t really work for me.
Lastly, I’m going to need external gateways to check in to setup their deviceIDs and get their secretkeys and accesskeys.
Also with the redirect, the I cannot get the HTTP POST request to work.
To see my attempt click the link below:
API Request Example