Apache2 sometimes serving old SSL certificate - ssl

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

Related

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!

Apache server does not show up on EC2 IP

I am trying to install apache2 on my EC2 instance.
I did the following steps:
Launched an Ubuntu 16.4 instance with security group details
http - 80 - anywhere
https - 443 - anywhere
Once I login to my instance I did
sudo apt update
sudo apt install apache2
when I type
service apache2 status
it says that Apache is running
I assumed that after this if I go to my public IP address [xxx.xx.xx.xx] I would see the default apache server page.
But I see This site can't be reached.
The process seems pretty straightforward, what am I doing wrong?
I had this stupid case, it made me reinstall dozens of times.
Maybe my Security groups don't allow https://
Replace https:// with http:// if available.
It will work perfectly.

How to enable SSL in docker with nginx hosted in Ubuntu

I have a web application that's running inside a docker container.
It's written in Play Framework. My host is an Ubuntu 16.04 server with apache. Docker application use the nginx server. The port 443 is directed to that container. SSL in my Apache server is turned off. Now when i try visiting my domain with https the browser give the warning which is annoying.
So i got some free certificates from sslforfree.com and used it with the docker application but still the warnings come up. Do i need to use those certificates in the apache server too?
Yes.
Your browser speaks with Apache server trying to establish an SSL communication at first, then Apache will try to forward the request to your docker container.
So, indeed, it's only mandatory to secure your Apache instead of the container to have the browser not complaining.

How to stop tomcat and start apache2?

I have this server, that i have not installed personally. There are Apache2 and Tomcat6 running together. I want to stop Tomcat6 and use Apache2 but when i do
sudo service tomcat6 stop
sudo service apache2 restart
if i type 'localhost' in my browser i get a '503 service unavailable' error. So how i can get Apache2 'take control'? I mean i want the default site of Apache2 to be displayed on 'localhost' instead of tomcat'one.
(If i type locahost with Tomcat running i get an "it works" welcome page.)
Apache2 will have control when Tomcat is stopped and you start Apache. With Tomcat running on same port, you are unable to start Apache. Solution to 503 error is in Apache logs.

mod_spdy on apache not applying to all vhosts

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!