I have a Web App with registered domain and it is running on AWS EC2. The domain is https:\\abc.abc. I have a flask API on the same instance where it running as a microservice. The API is running as http:\\abc.abc. Now when I try to connect to the API using the Web App with the registered domain it shows me
ERR_SSL_PROTOCOL_ERROR.
I have an idea that this is error is because of the
https and http connection
but I don't know how to solve it. Can someone please help?
In need for a somewhat detailed answer as this error is completely new for me.
Related
I have a node.js based web app which I have hosted in an azure environment as a web service. I am trying to post some data to another server from my webapp to basically store the login details. I am getting an error problem with request: connect EACCES. However I am able to post data using postman to the same server. Any help would be highly appreciated!
From error message, I should add Access Restriction in your app services.
Related post:
EACCESS Error in Node JS
From related post, I think you can Add Access Restriction in your app services.
I have an Azure app service and in some cases I need to send a web request to a non-azure webserver. What do I need to do to make it possible.
Currently the web request fails with no clear error message.
In response to a HttpClient Put request I get a System.Net.WebException exception which says there were errors.
THe same request works from a desktop application.
If your webserver is reachable from the internet you should be able to access it through your App Service. Try to log a ping to your webserver and google (8.8.8.8).
If your App Service is in a VNET you should enable some outbound rules to your webservers IP adress.
The server I am connecting to is an other Azure service. After some more investigating, It appears that I can connect to it if I do not use SSL (i.e. http://) but the connection is immediately closed when using SSL (https://). I assume that the problem must be related to the use of SSL.
I'm trying to create https endpoints for three apps in a cluster of Service Fabric. Because I have more than one app I use HttpSys. So far I worked only on http but requests from frontend are from a secure transmission(https) so I have to put my backend on https.
I tried to follow this 1 but it doesn't work with WebListener so I move the implementation to HttpSys.
I don't have any errors and my cluster is working well but when I try to access my https endpoint I get nothing.
I followed API Connect getting started guide to create a local loopback API app and tested successfully. Then I am trying to follow Publish Your API to Bluemix. The publishing is successful. The app is running. But clicking the app yields Chrome error:
This site can’t provide a secure connection
ddd.abbr-dev2.apic.mybluemix.net sent an invalid response.
I suspect the problem is incorrect port. According to CloudFoundry Nodejs tips, the port should use process.env.PORT, but loopback defaults to 3000. Following this clue, I tried adding config.local.js:
module.exports = {
port: process.env.PORT
};
But the service end point is still inaccessible.
Please Help. Thanks
This is actually by design. Since your API's implementation is on the public internet, it is secured via Mutual TLS. The only way to access it is via the API Connect gateway, thus ensuring the API is managed.
If you want to make it accessible publicly, open the app in the Bluemix console and add an additional route to the app, using the mybluemix.net domain.
I am using Node.js + Socket.io in my application.
Say, my chat application (php) is hosted on server A and node.js is hosted on AWS.
Each client accesses chat application and in the background it registers the client with the node.js application hosted on AWS.
The problem is when I use a proxy server from hidemyass.com and configure my firefox to access the application.
The application is loading but it unable to connect to node server hosted on AWS and I get a 403 Forbidden error.
Is this a problem with AWS security configuration or a node.js settings ? I am unable to figure this at all.
I have tried my best to search for reasons why this would happen, but didn't get any clue. Can it be an AWS configuration issues or Is it to do with Nodejs server settings. Any guess or help is highly appreciated.
Thanks you very much.