ssl

This month, we talked about the Open Social Drupal distribution. This distro is currently the most popular way to create a community site in Drupal, so we dived in and looked at some of the features that come out of the box with Open Social. We also discussed another aspect that is important to creating a new sites: SSL certificates. We talked about using SSL certificates on the bare domain and on www, and on different types of hosting hosting as well.

We are on Digital Ocean, nginx/1.4.6 (Ubuntu), and I followed the Letsencrypt tutorial and the SSL cert verifies as valid. However the Drupal login to access the admin no longer activates and the page just reloads to itself. I enabled debug for the NGINX logs and below are the results. It ends with:
*recv() not ready (11: Resource temporarily unavailable). *

Hi

I was hoping someone might be able to help with an issue that I have.

Basically I want two different SSL's (as they belong to two different and independent companies) to sit on my AWS architecture but my architect is trying to tell me this is not possible, which I personally can't quite believe.

The current system has been working perfectly for around 6 months using the x 1 SSL cert, but now I want to use a 2nd SSL cert this is where the problem has raised its head.

Hi

I now have a ssl cert setup for my site but just wanted to know how do I now change the whole D7 site to run on https//www.domain.com/xxxx etc?

Thank you

Stephen

I have been using Perusio's Nginx config in FreeBSD and Ubuntu without any problem. The only thing I couldn't understand is it redirects to HTTPS whenever I visit the site. I want to make my site accessible via plain HTTP for all users and HTTPS for registered/logged-in users.

I haven't changed any HTTPS config in FCGI or other place, I just declared the SSL certificates and keys, now whenever I visit the site, I am accessing HTTPS (even for anonymous users). I tried clearing all caches in my browser and also using private browsing but I am again forced to HTTPS. Im using D7, PHP-FPM, Nginx

Hi,
we are developing a e-commerce site using D7, Commerce module, PHP-FPM, APC, MySQL, InnoDB, Memcached, Nginx, SSL. Our Dedicated server has Intel i5 2.5GHz 4 Cores, FreeBSD, 16 GB RAM, 120 GB SSD.

Hello security minded folks!

There is a tag in use in the issue queue called "Security improvements" this is often used for areas where there is some sort of a bug or feature that isn't quite worth handling in private by the security team, but where action is needed to harden Drupal's security.

I've been Google'ing a solution for hours, but I still haven't found.

Do you have any ideas?

After reading various documentation on the subject I figured out how to possibly do this. I started a write up in the documentation, and placed it under technical review. Are there people with knowledge on the subject who want to take a look at it? This to ensure that there are no mistakes.

The url is:
http://drupal.org/node/1804604

I have a site that has both a large anonymous-use and logged-in participant usage. In an older version, the client used Secure Pages to get some pages into SSL, but to force most traffic back into regular HTTP if the page did not require it.

How best to implement this with Varnish or AWS?