Hello All,
We are trying to deploy a website developed using aspnetzero in angular and .net core.
Have recently upgraded the aspnetzero framework to 6.9.1 and are following the below steps to deploy it in IIS:
- Publish the host project which generates both the server side dll's as well as angular bundles.
- GOTO IIS and create two separate websites one for server and other for client
- Create two separate folders and copy the server code in one and client code in other
- Point the websites to respective folders
- Make the required changes in the appsettings.Production,json (for server) and appconfig,Production.json (for client)
- Apply certificate (signed by COMODO) to the client and define https bindings for both the client and the server in IIS
Doing all this setup we are able to browse the application but when we hit the URL it is showing the site is not secure (as shown below).
We have already gone through the deployment steps mentioned on the aspnetzero documents portal but they are very basic and are not helping in solving our issue:
https://docs.aspnetzero.com/documents/aspnet-core-angular/latest/Deployment-Angular-Publish-IIS#angular-application-publishing
While doing this deployment we have a come up with few queries:
- How do we deploy client and server as two different secure (https) websites in IIS
- Will we be requiring 2 separate SSL certificates, one for the server and other for the client.
3 Answer(s)
-
0
SSL certificates are related to domain names. If your certificate is a multi-domain certificate or a wildcard domain name (such as .*aspnetzero.com) you can use multiple websites. Otherwise you may need a separate SSL certificate for each domain name. (Can be in SSL provider Learn more)
When your browser prompts are not safe, can you look at the detailed reasons? You can click on the browser's [Not secure] to view the details.
-
0
Thank you we were able to deploy using valid ssl certificate. The issue was with setting up the configs
-
0
Hi I am facing the similar issue. I got my certificatte set up on both Client (angular)and Server(Core API). The CorsOrigins setting in appsetting.json is using ip address, if my certificate is signed to www.rtime.com.au and my accessing url will be www.myco.com.au:4432 to my anguar client, do i then change the CorsOrigins to the www.myco.com.au, like
"App": { "ServerRootAddress": "https://www.myco.com.au:4439/", "ClientRootAddress": "https://www.myco.com.au:4432/", "CorsOrigins": "https://www.myco.com.au:4432" },
thanks Laurie
