The main issue I faced when trying to enable Https on Magento 2 (NGINX) with Let’s Encrypt was getting a ‘Failed authorization procedure’ during the ACME challenge.
During the certification creation, the bot asks you to specify the root directory of your web folder. For me it was obvious that this would be Magento’s directory. However, when the bot tries to access the files it generated using my shop URL (something like: http://mystore.com/.well-known/acme-challenge/Ljkdslfjfewl2323kjhlkdsfjl324ERkhdpqu20IUDLkq), it gets a 404 from Magento.
If you want to avoid this error, carefully follow the steps below.
First, let’s install certbot
$ apt-get install certbot
Setup Magento 2.3.2 on Ubuntu 18.04
I assume you have the backups from your Magento 2 instance that you want to migrate. You should have these 3 files.
If you want to know how to back up your Magento 2 installation, have a look here [LINK_TO_BE_PROVIDED]
I also assume that you just freshly installed Ubuntu Server 18.04.
To prevent future problems, update and upgrade your operating system to make sure you have the latest security and software fixes.
Run the following commands with root privileges
$ apt-get update$ apt-get upgrade
If you landed here, it means that you’ve tried to secure external access to your Domoticz server with HTTPS following the steps described here https://www.domoticz.com/wiki/Native_secure_access_with_Lets_Encrypt
And, like me, you got blocked after running the command:
$ sudo ./letsencrypt-auto
You certainly saw the below printed in your Terminal.
Skipping bootstrap because certbot-auto is deprecated on this system.
Your system is not supported by certbot-auto anymore.
Certbot cannot be installed.
Please visit https://certbot.eff.org/ to check for other alternatives.
Keep reading. The solution is below. Well, in fact it was above ;)
Let’s start from scratch.
Install the needed system dependancies.
If you would like to migrate from Gitolite to GitLab, follow the steps below:
$ git clone —-mirror ssh://git@my_server:2222/my_repository
2. Go inside your repository
$ cd my_repository
3. Quickly check remote origin values (to make sure it show Gitolite server)
$ git remote -v
4. Remove the remote origin values and set value to new repository
As a pre-requisites here, you need to make sure you’ve already created your new repository in Gitlab. Mine is ‘my_gitlab_repo’.
$ git remote rm origin
$ git remote add origin git@my_gitlab_url:my_user/my_gitlab_repo.git
5. To be sure it’s set correctly, check remote origin value
$ git remote -v
You should see something like:
origin git@my_gitlab_url:my_user/my_gitlab_repo.git (fetch)origin git@my_gitlab_url:my_user/my_gitlab_repo.git (push)
6. Last step, push now everything to GitLab repository.
$ git push -u origin --all