How to Install DotNetNuke (DNN)by Erin Burns | .NET, DotNetNuke (DNN)DNN is a free open source .NET content management system (CMS). Like any CMS, users can easily manage site content and users, as well as develop and install custom themes and extensions (similar to WordPress “plugins”). The system requirements for DNN are as follows:
Operating Systems
Windows 8, 8.1, 10Windows Server 2008 R2, 2012 R2.NET Framework
4.5.1+Web Server
Microsoft IIS 7.5, 8.0, 8.5, 10Database Server
Microsoft SQL Server 2008 R2, 2008 Express R2, 2012, 2012 Express, 2014, 2014 Express, 2016 (for DNN 8.0.4+)Microsoft Azure SQL DatabaseIn this tutorial, I am using Windows 10, Microsoft IIS 10, Microsoft SQL Server 2014 Express and DNN Platform 9, and I am assuming you already have your database server set up. If your system is different (e.g. Microsoft Azure SQL Database), the installation process below is still the same.
1. Download the Install packageDownload the Install.zip package for the latest release from github.
You can also download the latest install package directly from DNN’s website – be sure to scroll down and select the Install Package download option.
2. Extract the filesGo to your Downloads folder and find the zip file. Right click the zip file, select Properties, then check Unblock and click Apply. This marks the file as trusted and ensures all the content is extracted and accessible.
Next, create the directory for the website. I am using D:\Tutorials\DnnTutorial. Now copy and paste all the extracted files and folders from the zip file into your new website directory.
3. Configure IISTo install IIS (or to confirm you have the appropriate settings configured), select Turn Windows Features on/off in the Control Panel, and turn on the following options below Internet Information Services:
Web Management ToolsIIS 6 Management CompatibilityIIS 6 Management ConsoleIIS Metabase and IIS 6 configuration compatibilityIIS Management ConsoleWorld Wide Web ServicesApplication Development Features.NET Extensibility 3.5.NET Extensibility 4.6ASP.NET 3.5ASP.NET 4.6ISAPI ExtensionsISAPI FiltersWebSocket ProtocolCommon HTTP FeaturesDefault ContentStatic ContentHealth and DiagnosticsCustom LoggingPerformance FeaturesDynamic Content CompressionStatic Content CompressionSecurityBasic AuthenticationRequest FilteringWindows AuthenticationOnce IIS is configured, you need to create the site. Open IIS, right click Sites and select Add Website.
Use dnndev.me for the Site and Host names. Enter or select the website directory you created in step 2 for the Physical Path. Click OK.
4. Grant File PermissionsYou may or may not have noticed that an Application Pool was automatically created with the same name as the website we just created. We need to grant this Application Pool access to our website directory.
In File Explorer go to your website directory, right click the folder, select Properties, select the Security tab, then click Edit.
Click Add
Now we need to enter the name of the Application Pool – in our case, we need to enter iis apppool\dnndev.me. Please note that there are three p’s in that name.
Click Check Name to ensure it resolves to our Application Pool dnndev.me, then click OK. (If you are on a domain, you may need to change the Location field from the domain to your computer).
After that, select dnndev.me from the Groups and Users list, check Modify permissions, and click Apply. Close out of the remaining windows.
5. Setup the DatabaseNow we are going to create a new database and login credentials. Open up your database server, right click on Databases and select New Database. Enter your Database Name and Owner, then click OK. You will need the Database Name later in this step and step 6.
After creating the database, expand Security, right click on Logins and select New Login. On the Generalpage, enter a new Login Name (I like to use straightforward login names so it is clear which system or application is using it), select SQL Authentication, and enter a Password. Please note, you will need to remember the Login Name and Password for step 6.
Then select the User Mapping page on the left – check the name of the database we just created and set the Default Schema to dbo, then check db_owner and public options for Database role memberships. Click OK.
6. Run DNN Installation WizardWe’re almost done! Now open a browser and go to your site (http://dnndev.me). You should be redirected automatically to the Installation Wizard.
Enter the desired settings in the Administrative and Website Information sections. In the DatabaseInformation section, use the following values:
Database Setup: CustomDatabase Type: SQL Server/SQL Server Express DatabaseServer Name: .\SQLExpress (if you are using a professional version of SQL Server or Azure, enter the appropriate server name instead)Database Name: DnnTutorial (the Database Name created in step 5)Security: User DefinedDatabase Username: web_dnntutorial (The Login name created in step 5)Database Password: (The login password created in step 5)Run Database As: Database Owner (make sure this is checked)
Now click Continue to run the Installation Wizard.
Once the Installation Wizard is complete, click Visit Website – you should be redirected and automatically logged in (using the admin credentials you specified earlier in step 6).
You have a Mac Computer and are running Microsoft Desktop (RDP) throws an Error code: 0x4 just randomly when you try to connect to a computer you have configured for connection.
For us, this problem just randomly started this year after Microsoft updated their RDP software. “Go Microsoft”
We have searched the web, and noticed that the suggestions to Reboot the computer, or restart the RDP software, or both. Do not appear to reliably work. Although we did have some luck with this.
Another suggestion was to copy or recreate the connection in RDP. Again, only limited success with this solution.
For us the solution came when we went into the system preferences of the Remote Desktop Connection
And you will notice the default preferences look something like this.
We simply unticked the “Use hardware acceleration when possible” check box.
That’s it. After doing this you should notice that it fixes Mac RDP not connecting with 0x4 Errors.
Is why would you want to do such a thing. And usually the reason is that you’ve ever sold the application to a new organisation and subsequently transfer it to their development account. Offer some reason you’re moving it to another account of your own perhaps hundred different name or tax system.
In our example was gonna be transferring it to a new account purely for tax reasons. There is nothing dodgy going on, just legitimate reorganisation of our tax portfolio.
In order to complete the transfer, you’re going to need to have your new account set up and most importantly the new banking and tax details set up for whichever region you live in.
To ensure that these are set up correctly, log into your App Store connect page. And from the list of icons, select the agreements, tax, banking.
Here you can doublecheck that for both your free apps, and paid apps, that the status is showing active for your country and region.
Personally I find it easiest to use to web browser sessions. But that’s in Tiley up to you. I also prefer to do it one application at a time, assuming that you have multiple applications to transfer it can really help if you get bogged down with one to understand why it’s not transferring without getting muddled up with any emails or other notifications from other applications.
Log into the App Store connect with your old account, or the account that you are transferring from.
Select the application from the list of apps, that you wish to transfer. In our example we are going to use the trip tracker app.
From the left-hand menu, select have information.
Then on the right hand pain, scroll to the very bottom.
Look for the transfer app link in the additional information at the very bottom.
You will need to ensure that all of the criteria for transfer are met. There are several common mistakes here that can prevent you from making the transfer. The most common one is that your application relies on the iCloud to store information. You cannot transfer an application while the iCloud feature is enabled within your application. The easy solution for a problem like this, is to release a version that doesn’t use the iCloud feature. Publish this version, transfer the application and then re-publish a new version that adds the iCloud feature back into the application.
Next you’re going to have to fill in the recipients Apple ID. This is the email address associated with the other development account. You will also need the team ID. If you’re unsure where to find this hover on the? To the right and it will explain that it can be found in the developer login under membership.
Next you’re going to have to agree to the terms for the transfer. Scrolling to the bottom and ticking the box before request transfer button.
You are now complete with the old account.
Log into the new App Store connect page with your new account details.
If it has been few minutes since you requested the transfer. You will probably see and yellow message with application transfer request pending acceptance.
It is okay if you do not see this. As you can simply click on the agreements, tax, and painting link.
Clicking this link takes you to a page that will list among other things the applications that are waiting for transfer. It will also include the link to the review section that will need to be filled in to complete the application transfer for the new account.
Click on the review link.
Next you will need to fill in the details that support the applications new home. This includes the support URL, the application review contact information and phone number and email. Then you will need to agree to the terms. Interestingly every time we transfer applications the terms are garbled rubbish that we can’t actually read. And I suspect it’s that way for everybody. However in all honesty who cares, as we would not have read it anyway.
Once you are greeted this transfer request terms. You are done and the application will appear within the new accounts App Store connect page.
Basically this error is telling you that the path in the config.php file is invalid for some reason. The most likely reason being that the http:// is defined and it should be https://
If you open the file config.php in your favourite editor
And navigate to line 21, depending on your version and edits to the file.
You can update your pat URL to include the “s” in https
Save and you should be able to access the site correctly.
So if you are working with Mautic 3.1 like we are as of today, and you are installing modules that connect to the Mautic API, you will find that after you make Custom Fields Editable
Or Enable the API for Mautic in CONFIGURATION / API SETTINGS
That you will then need to clear the Cache directory of Mautic before your other Applications will be able to connect to the API.
Now we are using cPanel and have access in there to the File manager. Easier than running an SSH command is to go into the director: var/cache in the Mautic directory. In our case here we have it in a directory or folder named marketing.
You will see a bunch of files here like this:
Just delete all of these files from the cache folder.
That’s it. You should then be able to connect to the API.
Lets hope that one day Mautic add a clear cache button to the application.
Is the implementation of SSL important for your website? The answer to that is simply YES…
And we are about to list some of the common reasons that SSL encryption on your website is more important than ever.
But first, let’s explain exactly what SSL encryption is…
Putting is simply, is is when you access a website using HTTPS:// before the address in place of HTTP://.
Websites that use https:/// are using some cleaver encryption that ensures that information sent to the website browsers and from the website browser to the website is secured and cannot be intercepted by people spying on your connection.
Sites without this encryption send information back and forth as plain text. Making it super simple for anyone who is looking at this information to read all of it.
This includes passwords (and we all know we use the same passwords on different sites), to personal information such as when filling in a form. Email Address, Date of Birth, Address, Phone Numbers etc are just some of the information we want to ensure remains secure.
Since 2018, when Google made SSL/TSL mandatory. Most web browsers such as Chrome, Firefox, Edge will throw warnings to customers who try and access your websites.
Some warnings are subtle, but others can be quite significant and you may not be aware of this if you are not using the same browser and computer system as your customers.
The above image is some of the examples of warnings that your customers can get from your website when it is not secure.
We actually see the removal of user warnings as the Number 1. Reason to implement SSL on your website.
Way back in 2014, Google made changes that included SSL in the algorithm for search engine rankings.
So simply put… your site will rank better with SSL that without, and subsequently you can expect more people to browser your site.
There have been many studies that confirm that. One of these studies is by backlinko.com.
So SSL helps you get to the First Page of Google. Something everyone wants in their industry.
The entire reason that Google gives better rankings for sites with SSL/TSL encryption, and the reason that they throw warnings to users who visit sites without this encryption is that they are encouraging all of us to be secure with Data.
SSL will help protect your site, and your users data from the huge army of users who try to attack it on a daily basis. Many of our customers and web users would not be aware of just how prolific hacking is and how real the threat is.
Our website Interactivewebs.com for example receives around 7000 hack attempts a week. If one of these hack attempts are cleaver enough, and your site is not using SSL, then it is not too difficult with freely available hacking tools to gain data such as passwords entered as a user logs into your site.
Adding SSL to your website makes the monitoring of passwords and other information almost impossible.
Many Countries like Australia, Europe, UK, and the USA all require that people taking payment on the web comply with PCI / DSS standards.
One of the core functions of taking payments on a Website is to do it in a way that does not put the user of the site at risk of theft of their details.
Using SSL/TSL security is a cornerstone of encrypting data for your website users. In most first world countries, this is a legal requirement and the PCI DSS standards are used as a minimum standard for web security for sites that take payments.
Building Trust in your Brand is important. Sometimes with customers this is something that you can build over time.
For Web users, the experience of trust starts with the first Impressions.
Security on a Website with SSL is the first point that customers make judgments about how seriously you take security and how they will trust you with their data.
If you throw a security warning to every Firefox user who hits your site, then you are starting the user experience saying you do not value their data.
Simply the trust in your brand start from a position of mistrust if you are not using SSL.
One of the most important processes of implementing SSL on your Website is the validation of Domain Ownership.
This step proves that the SSL certificate that has been implemented is part of the Brand, Company and Domain that is using the certificate.
This is the second primary task for the SSL implementation, and although we rank it in 6th place, it could be argued that it is super important as it proves to users that your site is “real” and not someone else pretending to represent your company.
We take care of this validation process on your behalf when we implement SSL on your site.
Adding SSL Security to your InteractiveWebs hosted website has never been easier.
Place the order with us, and we will implement everything for you.
NOTE: For existing customers. If you have not logged into our client system before, please use the “Forgot Password” function to retrieve your login details.
Hot To Enable TLS 1.2 in Windows Server 2008 or 2016
We previously had a post that handled this solutions called: How to Enable TLS 1.2 on Windows 2008 R2
This post is an update to how the enable and Mange TLS 1.2 on Windows Servers. The reason for the update is because we now use a free tool when we are managing our servers. But first some background.
What you need to know about TLS 1.2
According to…https://docs.microsoft.com/en-us/windows/desktop/SecAuthN/protocols-in-tls-ssl–schannel-ssp- TLS 1.2 client and server are enabled by default. But… https://social.technet.microsoft.com/Forums/en-US/cb1a695b-a15c-4fa7-94f0-1aaa20c1279d/enabling-tls-12-on-windows-server-2012-amp-2016?forum=winserversecurity …says Turns out it is, but not enabled for SCHANNEL service Hence you MUST follow… https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enable-and-disable-tls-12 Please articulate this! Say… You can enable and disable SSL 2.0 and 3.0 and TLS versions 1.0, 1.1, and 1.2 using Manage SSL Protocols in AD FS. On Windows Server 2016, to use TLS 1.2, you must explicity enable it by following instructions at [https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enable-and-disable-tls-12] Source: GitHub
According to…https://docs.microsoft.com/en-us/windows/desktop/SecAuthN/protocols-in-tls-ssl–schannel-ssp-
TLS 1.2 client and server are enabled by default.
But…
https://social.technet.microsoft.com/Forums/en-US/cb1a695b-a15c-4fa7-94f0-1aaa20c1279d/enabling-tls-12-on-windows-server-2012-amp-2016?forum=winserversecurity
…says
Turns out it is, but not enabled for SCHANNEL service
Hence you MUST follow…
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enable-and-disable-tls-12
Please articulate this! Say…
You can enable and disable SSL 2.0 and 3.0 and TLS versions 1.0, 1.1, and 1.2 using Manage SSL Protocols in AD FS. On Windows Server 2016, to use TLS 1.2, you must explicity enable it by following instructions at [https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enable-and-disable-tls-12]
Source: GitHub
So the New Solution
We use the tool from Nartac Software called IIS crypto.
This tool allows for easy configuration of Windows Servers to support the TLS 1.2 standard.
There are simple instructions to follow, but basically the solution is to implement the template for the Best Practise for Windows Server 2012 R2 and Windows Server 2016 and Later.
Recommended Settings
Microsoft has renamed most of cipher suites for Windows Server 2016. We list both sets below.
Windows Server 2016 and higher: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHATLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHATLS_RSA_WITH_AES_256_GCM_SHA384TLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_128_CBC_SHA Windows Server 2012 R2 and lower: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256TLS_RSA_WITH_AES_256_GCM_SHA384TLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_128_CBC_SHA
Windows Server 2016 and higher:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHATLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHATLS_RSA_WITH_AES_256_GCM_SHA384TLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_128_CBC_SHA
Windows Server 2012 R2 and lower:
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256TLS_RSA_WITH_AES_256_GCM_SHA384TLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_128_CBC_SHA
This tool allows you to easily configure servers like Microsoft Exchange Server, and IIS Web Hosting Servers to support TLS as it should be configured.
Enjoy!
How to Set Up Free SSL Certificates on IIS Using – Certify The Web
Using SSL to secure your website these days is very important. Many browsers throw messages to users who visit sites that are http:// and not https://. Although these warning can be ignored, they are concerning for users who do not understand the meaning of a browser when they say something like “This Site is Not Secure”.
It is kind of unprofessional too for hosts not to offer to install SSL certificates for their clients.
The solution and the How to Set Up Free SSL Certificates on IIS Using – Certify The Web is really rather easy.
On your Windows server running IIS and your website in question, browse to: Certify The Web Download
And access the download.
Run the download as an Administrator user either logged in as one or “Run as Administrator”
Accept the Agreement and NEXT
Accept the Default Location and NEXT.
Accept the Default Folder and NEXT
Click Install on the Summary Screen
Click Finish which will Run the Application.
Click on New Certificate
Click OK
Accept the Let’s Encrypt Certificate Authority and Enter Your Email Address
Tick the Accept and Register Contact
Then Click New Certificate Again, since we have now registered.
From the Dropdown List select the Site in IIS that you wish to secure. Note that in this example our site name is the domain name of the site. But your name could be anything. Just select the correct one.
It will come up with the domains that are Matching the Bindings of the Web instance. You can see in the list from the certificate tool matches the bindings we have in IIS for that site.
You can select the domains / bindings you want to use. One or in our case in this example we will create certificates for all the site.
As you do this, the tool will put the primary domain into the name place for the certificate you are creating.
Then Click on the Text Button, to test that each of the domains you have selected will allow authentication and access to the domain URL to approve ownership of the certificates authentication. You will see a Test Progress that shows that the selected domains we have are accessible.
Then Close that out the way with the arrow.
Then Click on Request Certificate
Then wait for a while while it does its thing.
If you get any errors, you will need to resolve them. In our example we intentionally left a sub domain that was used to setup the site initially. There is currently no DNS record for this sub domain, and subsequently the IP address could not be resolved. The solution is one of two option.
1. Configure a DNS A record to point this sub domain to the correct IP address of the IIS server. 2. Remove this from the list of selected bindings and subsequently NOT generate a certificate.
1. Configure a DNS A record to point this sub domain to the correct IP address of the IIS server.
2. Remove this from the list of selected bindings and subsequently NOT generate a certificate.
We are taking option 2 in this example.
We go back to the Manage Certificates, and untick the sub domain that failed above. This is where things got a bit sketchy. You would think that the tool is smart enough to work out that we are no longer requesting the certificate for this unticked sub domain. However we found that it would still fail on the sub domain when we re-ran the issue certificates.
What we had to do was to delete the certificate generation attempt here.
Close out the Certify SSL/TLS and then REMOVE the binding from the IIS site instance that is no longer in use.
Restart IIS – IISRESET from a command prompt
Then open the tool again and try to generate a new certificate.
We found that the certificates generated successfully at that point.