Install SSL on my server and get it working for all my subdomains

I'm get ready to install cert & update ssl. *******************************************************************************************************************************

Hi, A self signed certificate will not be recognized by browsers and any user opening your site with https:// will get a warning. If you need an authoritative SSL certificate you can by one. There's also the option of buying a multi domain SSL certificate which is more expensive but possible I can set up everything for you and show you where you can buy the multi domain certificate. Please let me know if you are interested. Thanks

Hi, We are fast growing hosting company in India. We have expertise in Linux server setup with management. We used to work with many hosting panels like cpanel, plesk, webmin , direct admin , ispconfig, zpanel, website panel etc. we will install SSL on your server as per your requirement. Thanks

I'm able to help you understand all aspects of SSL. I have a lot of experiences working with Web servers from both Windows and Linux. I think you won't be wrong if choosing me for your project. Hope to be cooperated with you! Kind regards, Khanh Tran.

Hi, I am having more than six years of experience in Linux administration and hosting services, I had implemented SSl for hundreds of domain/subdomain while working with tier 3 Data center. I can complete this complete this assignment as per your specification. I am adding you in my skype, you can discuss your exact requiremement. Thanks sachi

Hello, I noticed you mentioned HTTPS so I assume you want to secure web application(s). HTTPS is actually the usage of HTTP over SSL so you could say that HTTP + SSL = HTTPS. It would be useful to know which HTTP server you are using (Apache, nginx or other) because deploying SSL certificates is a bit different for each. Regarding your question of buying a certificate vs generating your own it really depends on budget and how your web-application is used. If your application is used internally (for example only by your colleagues) than you could create your own certificate authority (CA) import it on your colleagues computers and then use it to sign the certificate requests (CSR) for your subdomains - this is completely free. If on the other hand your application is "public" (accessed from computers you do not have control over) than you must purchase a certificate from a recognized CA. There are also free certificates (valid for a maximum of one year) but I have not used them and I doubt you can generates five certificates for free or wildcard certificates. My advice is to purchase a wildcard certificate from a recognized CA and use it for all the subdomains; this way you save money and it is simpler to deploy. One certificate supplier I have used and been very pleased with is RapidSSL. I also manage a few servers on DigitalOcean and I had to upgrade openssl because of the Heartbleed bug so I can help you there too. Thank you for your time! Best wishes, Ionu

I am a professional Linux and Windows Systems Administrator with more than 14 years of expertise in this field. Completing your project would not be a problem, you can be sure a true professional is working on your project and that it will be completed as indicated. Let me know if you have any queries or need more information. Looking forward to work with you. Regards

I am Linux/UNIX expert with 8+ years of experience in system administration, data center, virtualization, networks and web development.

hi, self generated ssl will make user need to accept the ssl before entering the site, and sometimes it annoying. you can purchase wildcard ssl to support all sub-domains or purchase limited ssl for several sub-domain. we can discuss on skype if you interested. my skype : avudz99 best, m

A proposal has not yet been provided

Hi, I have 5 years experience in Linux and open source. I've setup hundreds of server with various type of services : mail (postfix, exim), apche, dns (bind), ftp, ssh, mysql, keepalived ... I'm also an expert in web admin (PHP, mysql, apache). Please give me a chance to satisfy you. Tks

A proposal has not yet been provided

Im server manager and web security expert, I can help you. If you have more information please contact me, I hope you hire me and thank you very much.

Hello, I can help you setup SSL for all your sub-domains and protect against the heartbleed vulnerability. You can generate your own SSL certificate, but then anyone who visits your website (over ssl) will have a big red warning that the SSL certificate is not trusted. And that's the only difference in the generated one vs the bought one. When you buy one, someone vouches that you are who you say you are, and browsers don't display an intimidating warning. Also, if you want to get one ssl cert for all your subdomains, you are going to need a "wildcard ssl certificate". Let's talk if you want to go forward. Thanks for reading.

Bis jetzt wurde noch kein Vorschlag eingegeben

Hi, I have 10 years of experience in IT industry, located in NZ. Currently I am working on automation, designing and implementation of AWS infrastructure using Cloudformation, AutoScaling, VPC, S3, ELB, Cloudfront, RDS, SES, SNS and other AWS services. Plus I have good hands on Configuration Management tools like Puppet / Chef which helps in automation of your application stack. I have great experience in Linux System Administration and can set up SSL without a hitch. ######################### Whether you get your certificate signed by a certificate authority (Verisign/GoDaddy etc.) or sign it yourself (generate on your own), there is one thing that is exactly the same on both. Both certificates will generate a site that cannot be read by third-parties. The data sent over an https connection or SSL, will be encrypted regardless of whether the certificate is signed or self-signed. Then Why should you buy a certificate rather than generating my own? A certificate authority (Verisign) tells your customers that this server information has been verified by a trusted source. You can use self signed certificates for test or development environements. It is recommend to use Signed certificates for production environments. ##################################### Thanks, Abhishek

Hi: I have a good experience in ssl/https configurations, certificate generation and avoiding heartbleed bug. so I can help you and do this work in a few hours.

Hi there! I can help you in this regard. Plz tell me the time you are free so that we can have chat for the said project.

Предложение еще не подано

Hi, I am sathish having 10 years of experience in system administration. I have previously worked with comodo (instant ssl) providing support to customers installing certificate on their varipous web servers. Technically you can use own certificate (self signed) but users will get certificate error while accessing your website because you certificate was not certified by known root CA (installed on browsers). While buying a certificate, you will be providing documents or authorize your domain name ownership, based on the same CA will sign your certificate and chain it under their root certificate so all the browsers can understand your certificate. For your requirement, you can go for a wildcard certificate. I can suggest you more options based on your web server configuration. Thank you