
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2015 04:20 PM
I'm trying to change the SSL cert in IISExpress. I've followed the guide here. We've actually been running over SSL for a very long time, but now I want to use a signed cert from our internal CA.
I have a windows certificate, which I exported as a .pfx file, but to do this, I had to export the private key, which required me to password protect the output (you can't skip it).
So, I have a new 'LansweeperWebsite.pfx' file, but can't use it because it's password protected. Is there a better way to do this?
I have a windows certificate, which I exported as a .pfx file, but to do this, I had to export the private key, which required me to password protect the output (you can't skip it).
So, I have a new 'LansweeperWebsite.pfx' file, but can't use it because it's password protected. Is there a better way to do this?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2015 05:05 PM
We are currently investigating this issue. Several customers had issues replacing the default certificate with their own one in the latest Lansweeper release. A fix will be implemented in one of the following releases (5.3.0.14 or later).
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-26-2015 12:34 AM
The default password for the LansweeperWebsite.pfx that comes with the install is just "Lansweeper". If you export the .pfx from your internal CA with the same password, rename it to LansweeperWebsite.pfx, and replace the existing file in your install, it will work. I just did the same. Just got lucky guessing the password.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2015 05:05 PM
We are currently investigating this issue. Several customers had issues replacing the default certificate with their own one in the latest Lansweeper release. A fix will be implemented in one of the following releases (5.3.0.14 or later).
