Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
SSL / CAN'T GET SSL TO WORK.. TRIED EVERYTHING!
« on: August 30, 2017, 08:24:30 PM »
I'm having a lot of trouble getting SSL to work on a server that will only serve a single website domain.
Maybe there's a way to simplify this, since I'm only serving a single web-domain from my IP address??
I have all the certificate files setup, and the certificate was added successfully in certificate manager. However I'm still getting warnings about the website not being secure. Everything in CWS indicates the certificate is setup correctly, and Apache is running.
The certificate is NOT a wildcard. It only covers xyz.com and www.xyz.com. I made my server host name srv1.xyz.com, and generated a self-signed certificate for that. Is that part of the problem? Do I need to buy another certificate for srv1.xyz.com? Or can I not name my host, as this would require another certificate?
Also, this installation is on AWS, so there is an elastic ip address and then a variable ip address. I don't know if the certificate file expects to see 1, and then fails when it sees the other?
I really want to make this as simple as possible. I'm just trying to host 1 website from my dedicated server with https:// and no browser warnings.
Thanks!
Maybe there's a way to simplify this, since I'm only serving a single web-domain from my IP address??
I have all the certificate files setup, and the certificate was added successfully in certificate manager. However I'm still getting warnings about the website not being secure. Everything in CWS indicates the certificate is setup correctly, and Apache is running.
The certificate is NOT a wildcard. It only covers xyz.com and www.xyz.com. I made my server host name srv1.xyz.com, and generated a self-signed certificate for that. Is that part of the problem? Do I need to buy another certificate for srv1.xyz.com? Or can I not name my host, as this would require another certificate?
Also, this installation is on AWS, so there is an elastic ip address and then a variable ip address. I don't know if the certificate file expects to see 1, and then fails when it sees the other?
I really want to make this as simple as possible. I'm just trying to host 1 website from my dedicated server with https:// and no browser warnings.
Thanks!
Pages: [1]
