-
Notifications
You must be signed in to change notification settings - Fork 36
Installation on NGINX runnig on CentOS
grindsa edited this page Jul 8, 2021
·
5 revisions
I barely know NGINX. Main input has been taken from here. If you see room for improvement let me know.
Setup is done in a way that uWSGI will serve acme2certifier while NGINX will act as reverse proxy to provide better connection handling.
- setup your project directory
[root@srv ~]# mkdir /opt/acme2certifier
- download the archive and unpack it into
/opt/acme2certifier
. - create a configuration file
acme_srv.cfg
in/opt/acme2certifier/acme_srv/
or use the example stored in the examples directory - modify the configuration file according to you needs
- set the
handler_file
parameter inacme_srv.cfg
or copy the correct ca handler from/opt/acme2certifier/examples/ca_handler directory
to/opt/acme2certifier/acme_srv/ca_handler.py
- configure the connection to your ca server. Example for Insta Certifier
- activate the wsgi database handler
root@rlh:~# cp /opt/acme2certifier/examples/db_handler/wsgi_handler.py /opt/acme2certifier/acme_srv/db_handler.py
- copy the application file "acme2certifer_wsgi.py" from examples directory
root@rlh:~# cp /opt/acme2certifier/examples/acme2certifier_wsgi.py /opt/acme2certifier/
- set the correct permissions to the acme_srv-subdirectory
[root@srv ~]# chmod a+x /opt/acme2certifier/acme_srv
- set the ownership of the acme_srv subdirectory to the user running nginx
[root@srv ~]# chown -R nginx /opt/acme2certifier/acme_srv
- install the missing python modules
[root@srv ~]# pip install -r requirements.txt
- Install uswgi by using pip
[root@srv ~]# pip install uwsgi
- Test acme2certifier by starting the application
[root@srv ~]# uwsgi --socket 0.0.0.0:8000 --protocol=http -w acme2certifier_wsgi
- Check access to directory resource in a parallel session to verify that everything works so far
[root@srv ~]# curl http://127.0.0.1:8000/directory
{"newAccount": "http://127.0.0.1:8000/acme_srv/newaccount", "fa8b347d3849421ebc4b234205418805": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417", "keyChange": "http://127.0.0.1:8000/acme_srv/key-change", "newNonce": "http://127.0.0.1:8000/acme_srv/newnonce", "meta": {"home": "https://github.com/grindsa/acme2certifier", "author": "grindsa <[email protected]>"}, "newOrder": "http://127.0.0.1:8000/acme_srv/neworders", "revokeCert": "http://127.0.0.1:8000/acme_srv/revokecert"}[root@srv ~]#
- create an uWSGI config file or use the one stored in examples/nginx directory
[root@srv ~]# cp examples/nginx/acme2certifier.ini /opt/acme2certifier
- Create a Systemd Unit File for uWSGI or use the one stored in excample/nginx directory
[root@srv ~]# cp examples/nginx/uwsgi.service /etc/systemd/system/
[root@srv ~]# systemctl enable uwsgi.service
- start uWSGI as service
[root@srv ~]# systemctl start uwsgi
- configure NGINX as reverse proxy or use example stored in examples/nginx directory and modify it according to your needs
[root@srv ~]# cp examples/nginx/nginx_acme.conf /etc/nginx/conf.d/acme.conf
- restart nginx
[root@srv ~]# systemctl restart nginx
- test the server by accessing the directory resource
[root@srv ~]# curl http://<your server name>/directory
you should get your resource overview now