My Dockerized Application consists of Nginx that serves frontend static files.
My domain is:
ipharmakey.gr
I ran this command:
Actually this is the entrypoint script of Nginx container that is being executed when running docker-compose up:
#!/bin/sh
certbot certonly --standalone -m xxxx@xxxx.com --agree-tos -n -d ipharmakey.gr -d www.ipharmakey.gr
nginx -g “daemon off;”
It produced this output:
My web server is (include version):
nginx-alpine latest docker image
The operating system my web server runs on is (include version):
Ubuntu 18.04.3 LTS
My hosting provider, if applicable, is:
AWS EC2 instance
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
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.35.1
Here is my nginx config file (it had been working fine until I tried to get a SSL certificate):
server {
listen 80;
server_name ipharmakey.gr www.ipharmakey.gr;
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
root /usr/share/nginx/html;
location ^~ /.well-known/acme-challenge/ {
allow all;
root /usr/share/nginx/html;
}
location / {
root /usr/share/nginx/html;
index index.html index.htm;
try_files $uri $uri/ /index.html =404;
}
location ^~ /api/ {
include uwsgi_params;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass :/;
proxy_read_timeout 900;
}
location ^~ /static/ {
include uwsgi_params;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_pass _:; #without trailing slash
proxy_read_timeout 900;
}
}
Also, both nginx and cerbot error logs are empty.
)
