
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-25-2021 10:45 AM
Hello,
So i did the following:
https://www.lansweeper.com/knowledgebase/how-to-configure-ssl-in-iis-express/
But i get the following error if i try access it:
"NET::ERR_CERT_COMMON_NAME_INVALID"
I made sure it is the same certificate that i adjusted with the guide.
Anyone exprienced this?
So i did the following:
https://www.lansweeper.com/knowledgebase/how-to-configure-ssl-in-iis-express/
But i get the following error if i try access it:
"NET::ERR_CERT_COMMON_NAME_INVALID"
I made sure it is the same certificate that i adjusted with the guide.
Anyone exprienced this?
Labels:
- Labels:
-
General Discussion
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-04-2021 04:54 PM
Just to rule out the basics: is the common name on the certificate the same fully qualified domain name you used in the URL in the web browser?
(remember that if the certificate has a fully qualified domain name, and you try to access it in the browser by IP address or just using the hostname, there will be a mismatch between the names which can result in the error you mention)
(remember that if the certificate has a fully qualified domain name, and you try to access it in the browser by IP address or just using the hostname, there will be a mismatch between the names which can result in the error you mention)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2021 09:57 AM
Luke Maslany wrote:
Just to rule out the basics: is the common name on the certificate the same fully qualified domain name you used in the URL in the web browser?
(remember that if the certificate has a fully qualified domain name, and you try to access it in the browser by IP address or just using the hostname, there will be a mismatch between the names which can result in the error you mention)
Yes it has but i think the problem is with the SAN in the certificate. It is "DNS-name=localhost". If i type that on the computer where Lansweeper itself is installed then it works as intended but if i try that on another computer then it makes sense that i wont work since it redirects it to itself "localhost". If i try to put the FQDN, IP or pc name of the computer where lansweeper is installed then there is a mismatch since it is looking for "localhost".

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2022 12:51 AM
saffo wrote:Luke Maslany wrote:
Just to rule out the basics: is the common name on the certificate the same fully qualified domain name you used in the URL in the web browser?
(remember that if the certificate has a fully qualified domain name, and you try to access it in the browser by IP address or just using the hostname, there will be a mismatch between the names which can result in the error you mention)
Yes it has but i think the problem is with the SAN in the certificate. It is "DNS-name=localhost". If i type that on the computer where Lansweeper itself is installed then it works as intended but if i try that on another computer then it makes sense that i wont work since it redirects it to itself "localhost". If i try to put the FQDN, IP or pc name of the computer where lansweeper is installed then there is a mismatch since it is looking for "localhost".
Hi, did you fix the issue. I am having exactly the same.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-14-2023 08:33 PM
Same here. Did anyone get it fixed?
