Best CA for SSL Certificates
-
@msff-amman-Itofficer said in Best CA for SSL Certificates:
but how for the life of me I am unable to get valid SSL certficate on webserver running centos 6.8 with apache.
The issue is that this server does not have domain, people access it using it is private IP:
192.168.1.139How can I create an SSL for IP internal server, some users fail to click Advanced then proceed to this website in Google Chrome.
And this internal server will remain internal and their is no need for it to be on WAN or the internet currently or the near future, what are my options ? even adding the certificate on users machines in Windows Trusted root certificate does not work for some reason, and is there any other option besides adding the certificates manually, can I use Wild Card SSL cert for this scenario ?
Why are they accessing it via IP address? Seems like it would be much more beneficial to use DNS, it will be easier for users and you won't run into this certificate issue.
-
@coliver said in Best CA for SSL Certificates:
@msff-amman-Itofficer said in Best CA for SSL Certificates:
but how for the life of me I am unable to get valid SSL certficate on webserver running centos 6.8 with apache.
The issue is that this server does not have domain, people access it using it is private IP:
192.168.1.139How can I create an SSL for IP internal server, some users fail to click Advanced then proceed to this website in Google Chrome.
And this internal server will remain internal and their is no need for it to be on WAN or the internet currently or the near future, what are my options ? even adding the certificate on users machines in Windows Trusted root certificate does not work for some reason, and is there any other option besides adding the certificates manually, can I use Wild Card SSL cert for this scenario ?
Why are they accessing it via IP address? Seems like it would be much more beneficial to use DNS, it will be easier for users and you won't run into this certificate issue.
Ah, I missed that part. @coliver is correct.
-
I have set two of my sites to use Let's Encrypt now. I have it set to redirect http to https. I would assume I disable http on the site so that it doesn't allow that traffic, yes?
-
@WLS-ITGuy said in Best CA for SSL Certificates:
I have set two of my sites to use Let's Encrypt now. I have it set to redirect http to https. I would assume I disable http on the site so that it doesn't allow that traffic, yes?
If you are redirecting, you have no need to disable http. You can of course. But then you also do not need the redirect.
-
Jared is correct, redirection is only a thing if HTTP is up and running.
-
@WLS-ITGuy said in Best CA for SSL Certificates:
I have set two of my sites to use Let's Encrypt now. I have it set to redirect http to https. I would assume I disable http on the site so that it doesn't allow that traffic, yes?
That is actually a good question.
If you are redirecting, does http need to be open on the firewall, since the original traffic is coming in on it?
-
@BRRABill said in Best CA for SSL Certificates:
@WLS-ITGuy said in Best CA for SSL Certificates:
I have set two of my sites to use Let's Encrypt now. I have it set to redirect http to https. I would assume I disable http on the site so that it doesn't allow that traffic, yes?
That is actually a good question.
If you are redirecting, does http need to be open on the firewall, since the original traffic is coming in on it?
Yes, if HTTP isn't there and working, how can it do the redirect?
-
@scottalanmiller said in Best CA for SSL Certificates:
@BRRABill said in Best CA for SSL Certificates:
@WLS-ITGuy said in Best CA for SSL Certificates:
I have set two of my sites to use Let's Encrypt now. I have it set to redirect http to https. I would assume I disable http on the site so that it doesn't allow that traffic, yes?
That is actually a good question.
If you are redirecting, does http need to be open on the firewall, since the original traffic is coming in on it?
Yes, if HTTP isn't there and working, how can it do the redirect?
Magic, of course.
-
@JaredBusch I setup a cert for a Windows server just this morning using this...
https://github.com/Lone-Coder/letsencrypt-win-simple
Absolutely flawless on initial cert binding and scheduled task creation for renewal. Guess I'll have to wait the 89 days to see if renewal works as easily as the initial setup did.
-
@NashBrydges said in Best CA for SSL Certificates:
@JaredBusch I setup a cert for a Windows server just this morning using this...
https://github.com/Lone-Coder/letsencrypt-win-simple
Absolutely flawless on initial cert binding and scheduled task creation for renewal. Guess I'll have to wait the 89 days to see if renewal works as easily as the initial setup did.
Assuming that it works like certbot and the standard LE renew conf files are used, it should renew at 90 days.
-
@NashBrydges said in Best CA for SSL Certificates:
@JaredBusch I setup a cert for a Windows server just this morning using this...
https://github.com/Lone-Coder/letsencrypt-win-simple
Absolutely flawless on initial cert binding and scheduled task creation for renewal. Guess I'll have to wait the 89 days to see if renewal works as easily as the initial setup did.
Just looked at that project and realized I looked at it back in December. Not stable enough for my tastes based on reading the pull requests and open issues.
-
@JaredBusch said in Best CA for SSL Certificates:
Yeah, Windows just is not there yet. Someone will get a solid application wrote eventually.
Ran across Certify for Windows just now. Anybody tried it yet?
-
@Danp said in Best CA for SSL Certificates:
@JaredBusch said in Best CA for SSL Certificates:
Yeah, Windows just is not there yet. Someone will get a solid application wrote eventually.
Ran across Certify for Windows just now. Anybody tried it yet?
Here's the GitHub page for it.
https://github.com/webprofusion/certify
It looks cool, but I'd be wary to use in anything even close to production. I might try it on a secluded test server, since the project is in alpha.
-
This line on GitHub about the project makes me even more weary:
Time spent on developing Certify is extremely limited. If you have a bug or feature and you can fix the problem yourself please just:
File a new issue
Fork the repository
Make your changes
Submit a pull request, detailing the problem being solved and testing steps/evidence
If you cannot provide a fix for the problem yourself, please file an issue and describe the fault with steps to reproduce. General issues which cannot be easily reproduced are likely to be ignored, sorry! -
@IRJ said in Best CA for SSL Certificates:
This line on GitHub about the project makes me even more weary:
Time spent on developing Certify is extremely limited. If you have a bug or feature and you can fix the problem yourself please just:
File a new issue
Fork the repository
Make your changes
Submit a pull request, detailing the problem being solved and testing steps/evidence
If you cannot provide a fix for the problem yourself, please file an issue and describe the fault with steps to reproduce. General issues which cannot be easily reproduced are likely to be ignored, sorry!At least they're up front about expectations.
-
@dafyre said in Best CA for SSL Certificates:
@IRJ said in Best CA for SSL Certificates:
This line on GitHub about the project makes me even more weary:
Time spent on developing Certify is extremely limited. If you have a bug or feature and you can fix the problem yourself please just:
File a new issue
Fork the repository
Make your changes
Submit a pull request, detailing the problem being solved and testing steps/evidence
If you cannot provide a fix for the problem yourself, please file an issue and describe the fault with steps to reproduce. General issues which cannot be easily reproduced are likely to be ignored, sorry!At least they're up front about expectations.
And the rest of it's just boilerplate submit an issue
