Try:
restarting Apache service
restarting the entire server
Done.
still get the same error.
Is there a “Back-end server” ?
i don’t know. its hosted on AWS and OS is ubuntu18.04 LTS
What does top
show?
[is it low on resources]
How many established connections are there?
netstat -pant | grep ESTABLISHED
Did you fully stop and start apache?
systemctl stop apache2
systemctl start apache2
Try removing the code we added.
Do you recognize the last two connections?
Both foreign addresses are private IPs 172.31.x.x
I find that very strange; as that implies they are connecting directly from within AWS system (not the Internet).
No.i dont recognize.
Are you familiar with the AWS firewall?
Did you remove the code we added?
[I don’t think that will change anything but we must rule that out]
No.
yes now removed.
The code WAS part of the problem !
hmm…
yes but the website still not redirecting to HTTPS
You need to familiarize yourself with the AWS firewall (when you get a chance - not right now).
As for the redirect code…
Let’s try a very simple one line first:
redirect / https://3mad.in/
put that after the second domcumentroot
Remove the line.
I see the same problem again:
curl -Iki 3mad.in
HTTP/1.1 503 Service Unavailable: Back-end server is at capacity
Connection: keep-alive
This “apache” is acting very strange…
Let’s follow these steps:
1: Enable mod_rewrite
sudo a2enmod rewrite
2. Restart apache
3: Insert redirection code
[either one will do for this test]