Submitted by sespit on Mon, 02/06/2017 - 15:33
Hello,
For some reason my one and only virtual host, which is using a Let's Encrypt cert issued through Virtualmin (latest version) keeps giving out the wrong cert to any browser I try. I did have to modify the permissions on public_html to be owned by Apache so that mod_php could be used with Nextcloud. I checked the config of the site to see what certs it is supposed to issue and they are all the Let's Encrypt issued files (screenshot attached).
The website is https://nextcloud.sesp.northwestern.edu
What could I be doing wrong?
Thanks,
Ryan
Status:
Active
Comments
Submitted by JamieCameron on Mon, 02/06/2017 - 19:03 Comment #1
Are you sure you're accessing the website via the same domain name that it has been created under in Virtualmin, and not an IP address or other hostname that resolves to the same IP?
Submitted by sespit on Mon, 02/06/2017 - 19:10 Comment #2
There really is only domain being hosted on this instance of Virtualmin. To the best of my knowledge, nothing was changed configuration wise expect the ownership on public_html, which I had to do with mod_php because Nextcloud requires it.
After reading this post: https://www.virtualmin.com/node/17261 to temporarily fix the problem I had to go to the /etc/httpd/conf.d/ssl.conf file and change the default certs to the location of the LE certs in the /home/nextcloud folder. That seems to have fixed the issue for now.
Submitted by JamieCameron on Mon, 02/06/2017 - 20:44 Comment #3
Interesting, that suggests that Apache was serving the default SSL virtualhost rather than the one associated with your domain.
Submitted by andreychek on Mon, 02/06/2017 - 22:13 Comment #4
Yeah you may want to verify in $HOME/logs/access_log that the right website is being accessed.
If it isn't, this documentation here may help:
https://virtualmin.com/documentation/web/troubleshooting#toc-the-wrong-s...