Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm trying to enable https://mysite.com on my Ubuntu 11.04/Apache 2
I followed several guides online, but I still cannot access https://mysite.com
The guides mentioned getting certificates from CA, does that mean I have to register somewhere?
Or, can I simply redirect all https traffic to http?
Yes. You need to get and install an SSL certificate.
The whole point of SSL is that a trusted third party verifies your identity.
You are going to need to read up on SSL or hire someone.
Good luck
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
My question is the following: I'm hosting a couple of websites on a web server (Apache on Debian Wheezy) and I want to have ssl on them. Can I have one certificate and use it for every domain or should I have multiple ones? I tried to have one but the problem is that if I first visit example1 with https, then if I try to visit example2 with https, I get the content of the former, while the url is the latter.
What am I doing wrong? What is the best way to have https for every website on the server?
you need SSL certificates for each domain hosted on the box.
you can have selected domains on SSL but would require tweaking the virtual host file.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have a web application with nginx. I would like to have unlimited subdomains. When I open subdomain.domain.com I see in my Chrome:
Your connection is not private
Attackers might be trying to steal your information from subdomain.domain.com (for example, passwords, messages, or credit cards).
Back to safetyAdvanced
NET::ERR_CERT_COMMON_NAME_INVALID
I can't understand how to fix this issue. I should add another SSL cert for all subdomains or I need different cert for every subdomain? Can someone explain what is the correct flow here?
Thanks!
A wildcard SSL certificate would allow you to have unlimited subdomains with a single certificate.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Any idea how to resolve this issue and avoid this alert? I am getting it under Qualys SSL Labs website's SSL test.
You have to upgrade your server software (server and SSL libraries) to a version supporting this fairly new option.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm thinking about using a self signed cert for a staging area of my app. However, this staging area is located on the same server as production, and I'm worried that using a self signed cert may cause the server to be flagged as malicious/suspicious. Should I just go ahead and pay for a real cert?
There is theoretically nothing wrong with a self-signed certificate, but browsers like Chrome will definitely raise a flag. I'd recommend getting a real certificate.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have many servers which SSL. Now anyone working with SSL and hundereds of servers will know the pain of renwewal and distribution of SSL certificates.
I want to automate this whole process(renewal and distribution).
Is there any open source product that can do this or any perl module that could assist me in doing this?
Thanks