Error: - This page isn’t working if the problem continues, contact the site owner. HTTP ERROR 408
Backed:
TWO IIS Web-server and AWS loadbalancer
We have deployed the same site on IIS webserver both the servers are placed behind the AWS classic load balancer.
We have installed the SSL using letsencrpyt one of the IIS server and exported the SSL and then installed the same on the 2nd IIS web server. Locally the site is working and can see that the website is fully secure.
Locally the site is working and can see that the website is fully secure.
Further, we pulled the Private Key: * and Certificate body: * data and installed the same SSL on AWS load balancer But when we try to server the same site through the load balancer it’s not working and we are getting the error: - Error: - This page isn’t working if the problem continues, contact the site owner. HTTP ERROR 408
No logs are being captured in the IIS logs.
Please assist.
Warm Regards,
Related
I am currently working on an .NET 5 & SignalR application and in localhost everything seems to be working fine. When I try to deploy it to IIS pre-production Server which doesn't have a SSL certificate configured, pages other than Login are showing the message "This site can’t provide a secure connection". In the login page from the browser console I can see that most of me javascript and css files aren't loaded with the error "Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR". Also from what I can see after user logs in, the request is redirected to Https.
I have removed app.UseHttpsRedirection(); from the Startup and disabled SSL in the Debug properties of the application. That seems to be a wired behavior because I used to deploy applications in .NET CORE before and didn't have these kind of problems. is there any way around this problem, except configuring an SSL certificate?
From the suggestions in server fault, configuring a self-signed certificate provided by IIS itself seems to be the problem solver. Still I don't get why the application was making that https redirection, but anyways in case someone else has this kind of issue.
I have hosted a site in IIS (Version 10.0.16299) on windows 10.
My site running under SSL required. When my site running with SSL required I am getting error
403 - Forbidden: Access is denied.
But when I disable required SSL, I am not receiving this kind of error everything is working fine.
But in my case, it is a must to use a required SSL connection.
The IIS hosted site is a simple directory browsing site.
How can I use it with the required SSL?
And I have attached the Trace root are in the below link.
Failed Trace root file
I reviewed your FRT log and the error message is 403.7-Client certificate required.
It is obviously that you are Setting Client certificates to required. If you don't need client certificate authentication for your web application, then Require is not required.
If you just want to enable SSL for your https site,Check Require SSL and set client certificate to ignore is enough.
Please keep in mind that you need to Set Client Certificates to required only when your web app require to pass client certificate from client side
It's a certification related issue we observed and resolved when installed the right certificate in the trusted root.
Configuration need to change on IIS
Occurrence of 403 is not only particular instance, it's IIS configuration part, in most case you can resolve from IIS it's self, there might be some restriction level in IIS setting, you can check on IIS where your site hosted, find IP Address and Domain Restrictions option and check there will an entry to allow specif IP address, we need to update that entry by checking Edit Feature Settings... enter image description here then need to select Access for unspecified clients: earlier may be Deny instead of this we need to allow enter image description here. after those changes, your url available to access if you have same issue which I described.
My Azure application needs to connect to an API that is deployed on a remote server. The Azure app uses https, while the API uses http. To avoid a mixed content issue, I changed my API address to https. But now I receive the following error:
Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR
So in summary, using http for my API gives me a Mixed Content error, and using https for my API gives me an SSL-related error.
Does anyone have experience providing an SSL certificate to an API thats already been deployed? Any advice would be greatly appreciated. Thank you.
So I have an application that I am deploying through a docker container in ECS service. And I am using Amazon Cognito through application load balancer for authenticating into the application.
When I configured this with internet-facing Application Load Balancer(ALB), everything worked fine. But now when I changed my ALB to internal, it is throwing an error 500 Internal Server Error.
Has anyone seen similar scenario?
The way I solved this problem was by adding a rule on Load balancer listener - On Unauthenticated - allow
I have a client who wants to set up SSL on a new directory on their website. They already have one directory using SSL. BUT, when I go into IIS, even the current encrypted directory isn't set up to require SSL. And, when I set either the new or old directory to require SSL it returns and error page stating that I need to call the page over https (which I did), no matter what.
We are not running in a farm. This is a single web server with no load balancing or proxy that I know of. 443 is not blocked. The log files shows a request for the page over 443, but redirects to http. What could be handling the encryption?
ASP.NET 2.0 APP running on IIS 6.0.
Any help is appreciated.
Thx,
T
Your comment "The log files shows a request for the page over 443, but redirects to http" implies yours pages are being sent over port 80. If this is the case what makes you think your pages are being encryted?
Another thought - are you running any ISAPI extensions such as Helicon?