I have developed a reactjs app with .net core web API as backend. I have hosted the app on windows server on IIS with http which was working perfectly without any issue but when I tried to host the same using a wild card SSL certificate it gives this error in console of the chrome :
"Failed to load resource: net::ERR_SPDY_PROTOCOL_ERROR".
error
I have also done some configuration regarding nginx on server as well which was described in some URL.
You can deploy your reactJS application in using AWS CloudFront, and can use route 53 to redirect AWS Cloudfront url to your domain. SSL can also be easily configured once this is done
Related
Im trying to hit an api to custom subdomain(api.example.com) for analytics to the backend.
It is working fine in localhost but in hosted environment the api is giving cors error.
I guess its the issue with hostedzone configuration.
As of now backend is not at all connected to the frontend.
need help.
this is the domain where my backend is hosted(http://54.95.135.232:8080)
ive tried mapping this url to the subdomain in godaddy so that once i hit the subdomain(api.example.com) it will redirect to the backend hosted port.
but its not at all working.
I have a react application. It uses Auth0 SDK for Authentication management.
I am using a backend powered by Auth0 SDK.
Currently, the backend is hosted on some-domain.com
Production React Application is also hosted on the same domain as that of the backend.
In development, I am running React Application in localhost.
I am able to log in using Auth0 in both the localhost and production environment.
But for some strange reason verifying the token (generated in localhost) at the backend throws an error in localhost while verifying the token (generated in the same domain as that of the backend) does not throw an error.
Both production and development react application uses the same Auth0 configuration.
I think since we are using the same auth0 configuration in both development and production. Both should generate a token that is compatible with the backend. But it's not happening.
I have a https frontend which is making requests to the backend. After adding ssl certificate my requests are getting blocked. I cannot make my backend api https. What should i do?
FYI:
The frontend server is react, the backend is express and i am running nginx.
In order to make https requests to the backend server, i just set it as a subdomain and it all worked.
I am facing problem when I call an api end point url from a https page. I have hosted my front-end code in aws s3 bucket and a third party ssl certificate is deployed .so my react code is served over https. And my back-end is deployed inside a single instance application of elastic bean stalk. while I am trying to call my back-end url from my front-end application, it is throwing the below error.
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ''. This request has been blocked; the content must be served over HTTPS.
Can anyone help me to resolve this issue.
Thanks.
You need to setup your ELB (AWS Elastic Beanstalk) application to use SSL/HTTPS
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html
You can set this up with Route53 and AWS Certificate Manager (ACM).
I have my java spring project running successfully on AWS EC2 instance uploaded via elastic bean stalk but its endpoint is of the form http://...........
Now i have uploaded my angular project on firebase.
I could have uploaded it on AWS itself but it requires geolocation() which requires HTTPS connection. when i connect my angular app to aws instance via endpoint it shows
Mixed Content: The page at 'https://aspertime-a3b60.firebaseapp.com/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://aspertime-env.x2enfd8jmj.ap-south1.elasticbeanstalk.com/employee/login?username=123&password=123'. This request has been blocked; the content must be served over HTTPS.
i have tried many times to solve this problem.
-
So as we discussed in the comment, follow these steps
Create a Certificate from AWS ACM
Verify the certificate by adding an entry to your DNS provider
Create Load balancer with https listener
Place Load balancer on the top of Elastic beanstalk
Update web-app to point New TLS endpoint