mod_spdy on apache not applying to all vhosts - apache

I just installed the latest version of mod_spdy for apache. I have several vhosts running off of that server, all of which utilize SSL. Unfortunately, only about half of the sites indicate that spdy is working when using chrome://net-internals/#spdy. What's interesting is that the sites that work utilize self-signed certs. Any site with a CA issued cert does not appear to take advantage of spdy. There are no errors in the httpd log, so it may just be a coincidence that only the self-signed certs work.
I'm new to spdy and have never implemented it before. I simply installed the rpm and restarted apache.
For reference, I'm running CemtOS 6.5 with Apache 2.2.15. Any help would be greatly appreciated.
Thanks!

Related

Apache2 sometimes serving old SSL certificate

We renewed the wildcard ssl certificate on our Apache2 webserver on ubuntu 16.04. Most of the time, the website serves this new certificate and everything is fine. However, sometimes it serves the previous expired certificate. This can be resolved by just refreshing the page. This is the only site being hosted on this server.
How could this be happening and what can be done to resolve this issue?
The problem was that multiple instances of Apache2 were running for some unknown reason. To fix:
sudo killall apache2
sudo service apache2 start

Fixing my Apache configuration to work with letsencrypt

I had https on my wordpress site working with a an ip address and self signed certificate fine. I set up the dns for the domain and installed and ran letsencrypt "successfully" but ssl connections to the domain are still trying to reference the original self signed certificate rather than the newly created ones (where are they?) and I'm not sure where to start troubleshooting
Running Apache2 on Debian Buster
Cheers
I'm not sure this was the correct way to fix it, but I went into the apache ssl conf file and changed the paths of the temporary certs i'd set up to the new letsencrypt cert file paths and restarted apache, and it worked!

Installing and Configuring Apache 2.4 on windows

I have been tasked with Installing and Configuring Apache 2.4 on a windows server for the following purpose:
Configure SSL through apache
Apache Tomcat also installed on server to handle web request to a specific web application - MySQL db also on the same server.
How does one go about installing and configuring SSL through apache 2.4 on Windows Server 2012?
I have read so many documents and so many questions on forums etc and is now more confused than before.
http://httpd.apache.org/docs/2.4/
https://www.sslshopper.com/article-installing-an-ssl-certificate-in-windows-server-2008-iis-7.0.html
So far i have download and installed apache as a service and created the Certificate service request from OPENSSL (downloaded and installed also).
All I need to do now is :
How does one import these certificates in apache ?
How do you test if the import was successful and if ssl is working ?
How to redirect Apache to Apache tomcat to serve the webpage
Can someone please outline the steps require and if possible how to perform these steps for apache in Windows.
Thanks.
Regards,
Robert Ramoutar.
How does one import these certificates in[to] Apache [httpd]?
http://httpd.apache.org/docs/2.4/ssl/ssl_faq.html#realcert
How do you test if the import was successful and if SSL is working?
Connect to the server using a web browser with HTTPS. If it works, and the certificate looks the way you wanted it to look and you don't get an errors/warnings, then you are good.
How to redirect Apache [httpd] to Apache Tomcat to serve the web page
You need to use a module for reverse-proxying like mod_proxy. Read the documentation for mod_proxy_http to see how to set one up.

Varnish SSL with Nginx

I have a website on my server and install Varnish , all right . Now I'm going to install the SSL certificates and I read that Varnish does not support SSL, I have to install Nginx to operate the certificates. Anyway , just be installing Nginx and my question is whether the SSL pages will have the benefit of the cache? Or the SSL pages, will not have cache.
Forgive me if my question is very simple, it is that I'm new at this and do not know much about web servers.
You can set up NGINX to take care of SSL termination. If you do so, you still have caching for SSL. Take a look at SSL termination article for more detail.

CSR Generation: Tomcat or Apache?

While not entirely programming related. I recently purchased a SSL certificate, and during the configuration I need to generate as CSR.
I am running Tomcat behind Apache via mod_jk. I see two options for generating the CSR one for Apache and one for Java based servers. My question is which do i use? At the moment the site needing the SSL is configured to have all requests forwared straight to Tomcat for processing. This however may change to only certain pages. Does it make a difference?
Thanks in advance.
If you are going to use mod_jk then the SSL cert should be generated for apache. mod_jk connects to tomcat over the APR protocol (default 8009) so all SSL handling is done by Apache. This works nice since, in the future, you may only want to proxy dynamic content with mod_jk, assigning the cert to Apache will allow you to proxy static content using HTTPS.
Fyi, the thread you referenced only discussed whether you had to generate the keypair and cert request on the same machine and is not related to running tomcat + apache + SSL. That thread is not relevant to your question.