I was trying to deploy my web app without using HTTPs using a custom domain:
But all the settings I made did not work, when I enter the url I still get the https version.
Reference: How to Disable SSL on ASP.NET Core API 3.1 Project in Visual Studio 2019 16.8.3 Build?
entering the URL will still forward to the https version
You can't disable the HTTPS scheme on an Azure website, that's one thing configured centrally and not something you have the ability to turn on or off.
You can simply load a free SSL certificate onto the site that's valid for your own domain .
Please refer How to load a free SSL certificate into an Azure website.
NOTE:-
you can only load your own certificate on Basic and Standard Azure
websites, you won't be able to do this if you're on Free or Shared.
For more information please refer the below link :-
. MAP custom domain| MS DOC .
. Similar SO thread. .
Related
I have hosted a static website in azure mainly by following the Microsoft tutorials. The process has been to create a storage account, create a CDN endpoint, map my custom domain to the endpoint and then enable HTTPS using an SSL certificate managed by azure.
The custom domain is working but the problem is firstly that although in Azure CDN it says that both HTTP and HTTPS are enabled, I can only access the website via HTTPS and when I try with HTTP the error I get says 'The account being accessed doesn't support HTTP'. The other thing is that in order to navigate to the secure site I have to put the entire URL in the search bar, starting with the https or the website can't be found. I'm not sure if this is normal but if I think of web browsing in general, this isn't usually necessary.
Any ideas on how to fix this would be greatly appreciated.
Default is that Azure only Allows HTTPS.
On App Service go to TLS/SSL settings and switch to HTTPS Only to Off.
On Storage Account go to Configuration and change Secure transfer
required to disabled.
I have a seemingly intermitted issue with a site I'm hosting on Azure.
The site works for most but we're getting a few reports that when people try to access the site via a link (in an email for example) the site throws an ERR_CONNECTION_RESET error in Chrome.
The site is an S1 App Service
The site running is .Net Core 2.1 (MVC)
It has Let's Encrypt certificate applied to it (and this shows in the browser)
It is set to be Https only and Always On in Azure's SSL and Application Settings blades respectively.
I've had a look around and it feels like maybe this is an SSL issue but I'm not sure.
I've done a re-bind of the cert.
Can anyone offer any advice? I've not encountered this before.
Update
An update from our clients suggest it could be happening as our domain is newly registered.
Specifically, it could be a reputation/categorisation issue coming in to play with the threat protection they utilise on their networks.
I will look into submitting an update to the relevant sites to see if it helps.
I have been struggling to configure an SSL Certificate based environment for hight trust apps in SharePoint 2013. I have on-premises installation of SharePoint 2013 (Enterprise). Following google and msdn articles, I figured out that high trust apps require Client SSL authentication. My app is a provider hosted app and requires an "https" url to be hit when triggered (there is no option for setting "http" url). Any help would be appreciated.
I highly recommend Kirk Evans' blog post on the subject to get you started:
http://blogs.msdn.com/b/kaevans/archive/2012/11/27/creating-high-trust-sharepoint-apps-with-microsoft-office-developer-tools-for-visual-studio-2012-preview-2.aspx
I was able to walk through this to get 90% to where I needed to be, including creation of a self-signed certificate for the PHA server.
What Kirk's blog didn't cover for me:
Setting up a dedicated PHA server. Kirk's post finishes with running the app
from IIS Express inside Visual Studio. I wound up needing a modified
web.config for non-dev builds, i.e. for code deployed to a dedicated
IIS instance.
Setting up for App lifecycle event receivers. If you want to handle
App lifecycle events from your PHA, then you may have even more
tweaking to do in the web.config file. To this point I've had to
enable Anonymous authentication in my service bindings in web.config
in order for SharePoint to call those handlers.
YMMV
Please visit this for bindings :
http://www.sslshopper.com/article-how-to-create-a-self-signed-certificate-in-iis-7.html
and In the publishing profile, modify the "SiteUrlToLaunchAfterPublish" and the "publishUrl"
SiteUrlToLaunchAfterPublish --> https://YourServerName:PortNumber/VistualDirectoryFolderName
& publishUrl --> Path where you publish your web
before this uncheck the "Use IIS Express" from your provider hosted web properties and select "Use local IIS web server". Pass the address of your simple http://YourServerName:PortNumber/.. url and create virtual directory.
If I create an azure website let's assume: myname.azurewebsites.net, I can access this by using http (http://myname.azurewebsites.net) or https (https://myname.azurewebsites.net).
What does this mean? Did I understood it right that basically I don't need an SSL certificate as it has one by default?
I need to build a web service that needs to use SSL. Therefore do I need to buy an ssl certificate and custom domain (not important)? I don't need a custom domain and the default one works fine for me. So can I use my service over SSL provided by Azure: https://myname.azurewebsites.net (is a wildcard certificate)?
If you need to build a web service that needs to use SSL I highly suggest that you use your own domain and your own SSL certificate (buy one) if you are going in production with it. If you just test/play around - than you can safely use the default provided one.
And you are correct about default provided one - you get a (free) SSL for your azure web site as long as it is only bound to the default XXX.azurewebsites.net domain. However the certificate you get there is a wildcard certificate issued to *.azurewebsites.net. I would not use it if I have to go for a production service!
If you are to use SSL features of Azure Web Sites with your own domain and certificate, check out the Pricing and requirement pages. There are important things to note!
I configured the Default website in IIS for SSL by creating a CSR using the IIS itself, submitted it to a CA, and assigned the issued certificate as the server certificate. That's all is required in this world to setup server SSL. But when I open the https url it says "Internet Explorer cannot display the webpage". Which pillar should I bang my head against to get it working? The only help from microsoft I could find is that useless arcicle http://support.microsoft.com/?id=290391 that presupposes you are configuring a non-default website for SSL and goes on and on about port conflict. I'm using default website for https.
I'm using windows xp, IIS 5.1 and Microsoft Management Console 3.0.
Please help or courier me a shotgun for shooting myself.
Edit: After I configured IIS for SSL, the Apache Tomcat server which had been configured on port 8080 has suddenly stopped working. The 8080 urls just timeout. What is the connection?
Edit: Because I can't live without Tomcat on my machine, I used another machine to setup IIS SSL after stopping the tomcat there. I face the same problem there, "Internet Explorer cannot display the webpage". Please help before I shoot myself.
Don't shoot!
XP has given me fits with SSL... have you tried setting the application pool to high/isolated setting up the website with an identity under COM?
That seemed to solve some issues for me.
Also - did you make sure to set it up in the correct stores? Is this an application that is running under your account or a service account? If it is a service account you may need to do a RUN AS on the certificate management console and add under that user's personal store as well as under the appropriate store for the machine/computer.
Good luck.