Hello, I'm trying to create a application that calls a server that is mine. I have a domain with a valid certificate (not self signed).
When I test the connection in the app creation screen on https://developer.lametric.com I get a error that I can't connect to the server... If I use http the connection is made. Please note that I have tested the https connection in the browser and in other apps and it works.
Is this possible? Can any one help me? The server that is receiving the request is a NodeRed instance (should be irrelevant) and the income is handled by a reverse proxy that ensures that the connection is in https and passes it to the server. This processes is working in the browser, but failing in the developer.lametric url validation.
I would prefere not to publish the url in a public forum, first its not my server to decide, I would have to ask the company, second if I do I'll send it by private message.
Dos this makes any seance?
Yes I'm sure.. I use the same port and method in other services like IFTTT as Google Actions, and all works ok... I only have one domain and I'm using a reverse proxy to route the traffic and assure that the connection is encrypted, I route the trafic to port 8888 and select the service based on the path, so is somting like this:
This works great on ifttt and google (and google is very demanding on this kind of things) but in the lametric I keep getting a error that is fails in the ssl handshake. I can't use port 443 because of company restrictions, I only tested it and I was able to get a green light in Lametric Developer Website, but I was not able to test it more. I don't see a reason to this not to work. If I call https://myserver.com:8888/lametric in my browser I can get a secure https connection and talk with my server, but with the lametric api I get a error in the ssl, this seems like some problem on the api call to my server.
You may need to troubleshoot the HTTPS validation link process with developer.lametric.com support or consider alternative approaches for connecting your application to the server.
Failing to call a server with HTTPS can be caused by several factors, both on the client and server side. Here are some steps you can take to troubleshoot the issue:
Check your internet connection: Ensure you have a stable internet connection and can access other websites without problems. Verify the URL: Double-check that the URL you're using is correct, including the "https://" prefix. Typos or incorrect URLs can lead to connection failures.
Clear browser cache and cookies: Outdated cache data can sometimes interfere with website functionality. Try clearing your browser cache and cookies and see if the issue persists.
Try a different browser:
If the problem occurs only in one browser, try accessing the server using another browser to rule out browser-specific issues.
Disable browser extensions: Temporarily disable any browser extensions that might be interfering with HTTPS connections.
Check firewall settings: Ensure your firewall isn't blocking HTTPS traffic. You might need to temporarily disable the firewall or configure it to allow HTTPS connections.
It seems like you're experiencing an issue where your server is not being reached using HTTPS. This could be due to several reasons, and here are a few steps you can take to troubleshoot and resolve the problem:
1. Check your server configuration: Ensure that your server is properly configured to accept HTTPS connections. This involves having the correct SSL/TLS certificates installed and configured, as well as the appropriate ports open for HTTPS traffic (typically port 443).
2. Verify your firewall settings: Make sure your firewall is not blocking incoming or outgoing HTTPS traffic. You may need to adjust your firewall rules to allow HTTPS connections.
3. Test your SSL/TLS certificates: Use an SSL/TLS certificate checker tool to ensure that your certificates are valid and functioning correctly.
4. Check your server logs: Review your server's logs for any error messages related to HTTPS connections. This can help you identify specific issues that need to be addressed.
5. Restart your server: Sometimes, a simple server restart can resolve connection issues. Ensure that your server is running the latest updates and patches to avoid any software-related problems.
6. Test your connection from different locations: If the issue persists, try connecting to your server from different locations or devices. This can help determine if the problem is localized or a more widespread issue.
7. Consult your hosting provider: If you're still unable to establish an HTTPS connection, reach out to your hosting provider for assistance. They may be able to identify and resolve any network-related issues.
Remember, maintaining secure HTTPS connections is crucial for protecting sensitive data and ensuring the privacy of your users. By following these steps, you should be able to resolve the issue and restore secure communication with your server.