Migrate from Nginx to Caddy for SSL auto-renewal in Amazon AWS EC2

 Dear friends,

Today, we will see a simple migration with less configuration of SSL auto-renewal.

I was using Nginx for SSL auto-renewal using certbot. Every 90 days, the renewal code should run, I made one more service it.

I have come across Caddy, which does an auto-renewal of SSL automatically with certbot. Reducing efforts and making the system smooth.

Follow the steps below

Stop and disable the Nginx

sudo systemctl stop nginx

sudo systemctl disable nginx

Install the Caddy

In EC2, if you are running Amazon Linux, then execute the following to install Caddy.

    sudo yum -y install yum-plugin-copr

    sudo yum -y copr enable @caddy/caddy epel-8-$(arch)

    sudo yum -y install caddy

Edit and configure the Caddyfile

Usually, it will be in the path /etc/caddy/Caddyfile

sudo vi /etc/caddy/Caddyfile

I have only one server that is running locally. So, my configuration is easy

domain_name {

    reverse_proxy localhost:port

}

You can configure more with your existing Nginx sites-enabled reference.

Happy SSLing.

If you like the blog or want to comment, kindly reach out to psrdotcom@gmail.com

Configure a API Backend Server with custom domain on Amazon Web Services (AWS) EC2 Ubuntu with NGINX and Certbot SSL

Hi all,

Build your own API backend server on AWS free-tier with SSL.

The below steps with reference links will provide detailed information of each step.

1. AWS account - Free-tier
2. Create EC2 Ubuntu
3. Connect to Ubuntu from your local using SSH/Putty
4. Install NodeJS
1. Open terminal
2. curl -fsSL http://deb.nodesource.com/setup_lts.x | sudo -E bash -
3. sudo apt update
4. sudo apt install nodejs //installs latest LTS nodejs
5. Create a sample node server
6. Install and configure node server process manager
1. sudo npm install -g pm2@latest
2. Navigate to nodejs server folder
3. pm2 start <filename>
4. pm2 startup systemd
5. pm2 save
6. pm2 list // List all the nodejs apps with status
7. pm2 stop/restart/start app_name/id // Actions of nodejs servers
7. Install Nginx
8. Configure your domain DNS records to map to AWS EC2 public/elastic IP address
9. Secure Nginx with SSL certs

Hope the above information is useful to set up the environment and play with your backend server.

Feel free to send your feedback and comments to psrdotcom@gmail.com

Connect to public hosted Ubuntu server MySQL Docker Image from local MySQL Workbench

Hi folks,

Today I am going to explain the procedure to test the public cloud hosted MySQL docker in Ubuntu Server to your local MySQL WorkBench.

We configured a Ubuntu Server on public cloud and installed docker.
Ping the public IP address to make sure, it is reachable to your pc/laptop.

Configure System

Install MySQL Docker Image

# docker pull mysql/mysql-server:latest

Check the images

#docker images

You should be able to view the downloaded mysql server image

Start the MySQL Server

# docker run --name=mysql1 -p 33061:3306 -d mysql/mysql-server
-d : Run in daemon mode
-p host_port:container_port
--name: container name

The mapped public ubuntu server port is 33061, which is mapped to the mysql server port 3306.

Check the containers

# docker ps

You should be able to view your mysql docker containers with container id and ports information

Get the MySQL root user password

MySQL generates a one-time password for docker container and writes to the log.

• To view the log, execute the following command

# docker logs mysql1

• To get the generate one-time password, filter the log with keyworkd "GENERATED"

# docker logs mysql1 2>&1 | grep GENERATED

• You should be able to get the line like below

GENERATED ROOT PASSWORD: Axegh3kAJyDLaRuBemecis&EShOs

• Copy the one-time password. In the next step, we will use this to login.

Reset MySQL root user password

• Connect to MySQL server

# docker exec -it mysql1 -uroot -p

• Paste the generated root password
• Change the password

mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'yourpwd';
mysql> FLUSH PRIVILEGES;

• Though you have the root user credentials, you won't be able to connect.

Root cause: root user belongs to localhost, not for the public host usage
Solution: create another user with all privileges

mysql> CREATE USER 'username'@'%' IDENTIFIED BY 'youpwd';
mysql> GRANT ALL PRIVILEGES on *.* TO USER 'username'@'%' WITH GRANT OPTION;
mysql> FLUSH PRIVILEGES;

• Exit the mysql

mysql> exit;

• Restart the docker

# docker restart mysql1

Connect from MySQL Workbench

1. Open MySQL Workbench
2. Click on add new connection icon
3. Enter the "Connection name"
4. Enter host name "public IP address" or "URL"
5. Enter username as "dev" (Above created user)
6. Click on Password "Store in vault" button and enter the "dev" user password
7. Click on "Test Connection" button
8. You should be able to view the "Successfully made the SQL Connection" pop-up

Hope this tutorial helps you to get connected with your public hosted mysql docker instance to your local mysql workbench.

Please send your feedback and comments to psrdotcom@gmail.com