Lightsail Installation

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: argfam.net

I ran this command: Ran thru all the steps to install Let’s Encrypt on my AWS Lightsail instance. Too many to list here I think.

It produced this output: when navigate to my domain (https://argfam.net or just argfam.net), see message stating “Not Secure”. Also, instead of seeing my domain name, I see the public IP address and folder I redirect visitors to. Not sure if that is normal or why I do not see my domain. I get my Domain from GoDaddy and hosting on Lightsail. DNS seems to work sinc eI get to Lightsail. Only have 1 A record at GoDaddy pointing the IP to argfam.net.

During install process I get a message saying Certificate, Chain and Key File all saved. Only error message I see is when running commands shown next. Not sure those “old” versions matter.

sudo chown root:root /opt/bitnami/apache2/conf/server*
bitnami@ip-172-26-3-199:/opt/bitnami/apache2/conf$ sudo chown root:root /opt/bitnami/apache2/conf/server*
chown: cannot dereference ‘/opt/bitnami/apache2/conf/server.crt.old’: No such file or directory
chown: cannot dereference ‘/opt/bitnami/apache2/conf/server.key.old’: No such file or directory

Ran ls command after these steps (:/opt/bitnami/apache2/conf$ ls -lh). Did not include all the results below. But maybe this would be helpful for someone who knew what they were looking at:

-rw-r–r-- 1 bitnami root 1.8K Jul 10 16:02 privkey.pem
lrwxrwxrwx 1 root root 46 Jan 3 22:50 server.crt -> /etc/letsencrypt/live/argfam.net/fullchain.pem
lrwxrwxrwx 1 root root 42 Jan 3 21:34 server.crt.old -> /etc/letsencrypt/live/DOMAIN/fullchain.pem
-rw------- 1 root root 993 Jul 10 16:02 server.crt.old1
-rw------- 1 root root 899 Jul 10 16:02 server.csr
lrwxrwxrwx 1 root root 44 Jan 3 22:49 server.key -> /etc/letsencrypt/live/argfam.net/privkey.pem
lrwxrwxrwx 1 root root 40 Jan 3 21:34 server.key.old -> /etc/letsencrypt/live/DOMAIN/privkey.pem
-rw------- 1 root root 1.7K Jul 10 16:02 server.key.old1

My web server is (include version):
Server version: Apache/2.4.25 (Unix)
Server built: Jul 8 2017 17:55:49

The operating system my web server runs on is (include version):
Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39

My hosting provider, if applicable, is: Amazon Lightsail

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

Has anyone installed Let’s Encrypt on a LAMP stack Lightsail instance? Would really appreciate help.

The issue that you’ve described - the redirection to the server’s IP address - has nothing to do with your SSL setup, or Let’s Encrypt.

In fact, the certificate is working just fine.

You need to look at why your application rendering a redirect on its home page:

    <meta http-equiv="refresh" content="0; url=http://52.15.61.238/LittleSchool"/>
    <title>LS Registration</title>
  </head>

  <body> 
  
  <p><a href="http://52.15.61.238/LittleSchool">Redirect to School Registration application</a></p>

This is specific to whatever web application you have running and nobody here will be able to answer it for you.

Ah, the index.html located in the htdocs folder just redirects to a folder under there where I had all my application files. It was just my way of keeping my application files separate from the Lightsail installed files located in the htdocs folder. I just copied all my application files to the htdocs folder and removed the bitname index files (they were taking precedence over my index.php).

As long as I enter a complete url (https://argfam.net/Login.php) it works fine. If I leave off the https://, the page is not secure. Trying to automatically redirect all access to https. So far no luck. This is another issue so consider my original request resolved.

Thanks for the quick reply. I believe I am almost there.

What you want is an https redirect, some searching the internet for ‘https redirect’ plus a few words about your setup, like Apache or bitnami, would get you on the right path.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.