Hello, I have a few domains set up with letsencrypt running on ispconfig 3.1.latest stable. I'm running on Ubuntu 14.04 LTS (It's hosed, but that's a different solvable problem.) At the moment, however, I have a domain that is setup and it is not setup to redirect to https. I did set up letsencrypt on the site just in case. All connections to this particular site are being redirected to https, but when they get to the site, it's handing out a key that was created earlier for a different site which, of course, generates a security warning for a bad certificate domain. I must have missed something simple. Any ideas of places for me to look to try to get a handle on what is going on? Thanks, Curtis
Did your LE SSL is successfully created for that site? Did it vhost contains the correct LE SSL link?
Check what ip address you have set in both sites, and either use the ip or * in both, but don't mix them.
OK, the SSL config is correct and all the correct files exist and the le creation was successful. That was the problem I had to solve first. This one was a new wrinkle. The mixture of the wild cards and the specific ip addresses was the problem. Very weird. I'm going to have to adjust the site creation templates as well as the dns zone creation to accommodate this easily for my customers. Thank you all for your help.
