I cannot enable HTTPS for website, when restarting apache, sslcertificatefile is empty or doesn't exist

MarioForever 2019-10-07 12:01:38 UTC #1

Keywords: WordPress - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 70d773cd-fa64-0d78-d783-675488bf0e8c

Description:
Followed the guide in the link - https://docs.bitnami.com/aws/how-to/configure-elb-ssl-aws/. The ssl certificate files there, are obviously dummy ones but I don't know how to get my ssl certificate file and ssl certificate key file and replace the dummy ones that are there. I tried to create a link (ln) command between my domain and the dummy server.crt file. (ln "/opt/bitnami/apache2/conf/my-domain.com.crt" "/opt/bitnami/apache2/conf/server.crt". This just erased the dummy file, causing the site to go down (error in chrome: connection refused).

michiel 2019-10-08 06:33:12 UTC #2

Hi @MarioForever,

Are you using an elastic load-balancer, in that case it's not needed to move the cert and key to your instance as the certificate is configured on AWS itself. If you are not using a load-balancer, please check the following guide:

https://docs.bitnami.com/aws/wordpress/drupal/administration/enable-https-ssl-apache/

Regards,
Michiel

MarioForever 2019-10-08 12:10:19 UTC #3

Hi Michiel,

Thank you very much for your reply. Yes, I have an elastic load balancer. I used the guide in the link which I included in my initial description to set up the load balancer.

Thanks,

MarioForever

michiel 2019-10-09 06:52:30 UTC #4

Hi @MarioForever,

If you are using the ELB load balancer then you don't have to replace the dummy SSL files. The SSL is configured through AWS and the request to the HTTP or HTTPS port of the load balancer is transferred to the instance. To prevent the error from showing, could you comment out the following lines in the /opt/bitnami/apache2/conf/bitnami/bitnami.conf file?

 #SSLEngine on
 #SSLCertificateFile "/opt/bitnami/apache2/conf/server.crt"
 #SSLCertificateKeyFile "/opt/bitnami/apache2/conf/server.key"

Regards,
Michiel

MarioForever 2019-10-09 09:43:30 UTC #5

Hi Michiel,

I've commented out the lines you've suggested. I am getting the following error message and the site is still down.

ERR_CONNECTION_REFUSED

Regards,
MarioForever

MarioForever 2019-10-09 12:05:32 UTC #6

Hi Michiel,

I've commented out the lines you've suggested and restarted apache. I am getting the following error message and the site is still down.

ERR_SSL_PROTOCOL_ERROR

Regards,
MarioForever

tomasp 2019-10-10 09:19:00 UTC #7

Hi @MarioForever,

I realize that the elb-ssl-aws guide says to add

if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)
    $_SERVER['HTTPS']='on';

after the WP_HOME and WP_SITEURL definitions but you have added it before. I don't think this would fix the issue but you never know...

Also, I would try setting your WordPress domain name as explained here

If you still find the same issue after making those changes please execute the bnsupport tool again and provide us with the new code.

MarioForever 2019-10-10 10:32:41 UTC #8

Hi Tomasp,

Thanks for your reply. I'm still getting the same error message.

here is the reference code from the bnsupport-tool:
d4bf7101-0ca6-8afe-bfb6-b6689e97e433

Thanks,

MarioForever

MarioForever 2019-10-10 10:35:41 UTC #9

Hi,

Also I saw this on the ELB guide:
"As an example, if you are using WordPress, you would need to edit the /opt/bitnami/apps/wordpress/htdocs/wp-config.php file and add the lines below before the WP_HOME and WP_SITEURL definitions:"

Thanks,

MarioForever

tomasp 2019-10-11 11:01:26 UTC #10

You are right, the documentation says to add that code before the WP_SITEURL and WP_HOME. I misread it.

Which protocol are you using in your WP_SITEURL and WP_HOME settings? I think it should be https

define('WP_SITEURL', 'https://DOMAIN/');
define('WP_HOME', 'https://DOMAIN/');

MarioForever 2019-10-11 17:40:13 UTC #11

Hi,

I have changed the protocol to https but am having no luck. The site was up and running before and I could view the page using the http protocol in the address bar in chrome. I think there is something wrong with the ssl certificate file and ssl certificate key file.

Kind Regards,

MarioForever

tomasp 2019-10-15 07:24:57 UTC #12

Hi @MarioForever,

So you can access using HTTP protocol but not using HTTPS?

If you followed the ELB guide, you should have configured the SSL certificates in the LoadBalancer using Amazon ACM (AWS Certificate Manager). Did you create a new certificate or did you use an existing one?

Also, which address/DNS are you using in orther to access to your application? If you are using your domain, please ensure that it is pointing to the load balancer DNS and not to your instance public IP. You can use https://dnschecker.org/ to check that.

MarioForever 2019-10-15 15:07:02 UTC #13

Hi,

I cannot access the site at all using HTTP nor HTTPS. I also created a new certificate using ACM and followed the instructions in the ELB Guide. However, the domain wasn't pointing to the load balancer which I've now changed so that the domain does point to the load balancer. But now I'm receiving an error "503 Service Temporarily Unavailable" when I access the site using https.
Thanks,
MarioForever

Powered by Discourse, best viewed with JavaScript enabled

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!

SugarCRM

Drupal

WordPress

Joomla!

Redmine