JohnBick said: A certificate generally goes with a single address. If it was issued for myservername.homeserver.com it would not work for myservername.com even if you have set that up. (And you would have to set that up separately.)

Indeed, its what I thought too, but the original certificate (maybe there was 3?) was definately different. I could see by examining it that there were 3 "CN = ..." values, each matching addresses where browsers wouldn't spit out errors if I used.

I actually still have it (though I cannot see the info above). In any case, that isn't really important now, hehe.

What I'm curious about, is how come it changed. The original certificate was something like:

MBA4FE727HDHE.... (you get the idea...)

Now, its a Go Daddy Class 2 Certification Authority one. And I'm wondering why the hell it changed? Because of that now, if I access it on my LAN using the machine's name, browser complain. It didn't use to. It also didn't complain on remote machines (over the internet) where the original certificate was installed (that is, I installed it myself). With this certificate however, only the homeserver.com address works without complains.

Its quite puzzling. I -am- more interested in knowing how come it changed, than in getting this working though. I have worked in IT long enough to know that things like this don't change magically :)