11-25-2021 10:45 AM
12-04-2021 04:54 PM
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)
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".
09-14-2023 08:33 PM
Same here. Did anyone get it fixed?
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now