Securing BookStack behind a Ubuntu NGINX Reverse Proxy

Alex Sage

Install Certbot

sudo apt-get update
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:certbot/certbot
sudo apt-get update
sudo apt-get install python-certbot-nginx

Run Certbot

sudo certbot --nginx

ubuntu@NGINX:~$ sudo certbot --nginx
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
cancel): [email protected]
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org

-------------------------------------------------------------------------------
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v01.api.letsencrypt.org/directory
-------------------------------------------------------------------------------
(A)gree/(C)ancel: A

-------------------------------------------------------------------------------
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about EFF and
our work to encrypt the web, protect its users and defend digital rights.
-------------------------------------------------------------------------------
(Y)es/(N)o: Y
Starting new HTTPS connection (1): supporters.eff.org

Which names would you like to activate HTTPS for?
-------------------------------------------------------------------------------
1: bookstack.aaronstuder.com
-------------------------------------------------------------------------------
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for bookstack.aaronstuder.com
Waiting for verification...
Cleaning up challenges
Deployed Certificate to VirtualHost /etc/nginx/conf.d/bookstack.aaronstuder.com.conf for bookstack.aaronstuder.com

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
-------------------------------------------------------------------------------
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Redirecting all traffic on port 80 to ssl in /etc/nginx/conf.d/bookstack.aaronstuder.com.conf

-------------------------------------------------------------------------------
Congratulations! You have successfully enabled https://bookstack.aaronstuder.com

You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=bookstack.aaronstuder.com
-------------------------------------------------------------------------------

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/bookstack.aaronstuder.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/bookstack.aaronstuder.com/privkey.pem
   Your cert will expire on 2018-05-22. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot again
   with the "certonly" option. To non-interactively renew *all* of
   your certificates, run "certbot renew"
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

ubuntu@NGINX:~$

Update your APP_URL

vi /var/www/bookstack/.env

Uncomment APP_URL and update your URL.

# APP_URL=https://bookstack.dev

black3dynamite

You should add Ubuntu in the title.

Alex Sage

@black3dynamite Updated. I assume the process is very similar on other distros.

PenguinWrangler

Is the title suppose to be:
"Securing BootStack behind a Ubuntu NGINX Reverse Proxy"

Or was it suppose to be:
"Securing BookStack behind a Ubuntu NGINX Reverse Proxy"

?

Alex Sage

This setup is a LXC host, running both NGINX and BookStack in a different containers.

I forward 80/443 from the host to the NGINX container.

Then setup NGINX to reverse proxy to another container (BookStack, NextCloud, etc.)

Each app has it's own container.

black3dynamite

@aaronstuder said in Securing BootStack behind a Ubuntu NGINX Reverse Proxy:

This setup is a LXC host, running both NGINX and BookStack in a different containers.

I forward 80/443 from the host to the NGINX container.

Then setup NGINX to reverse proxy to another container (BookStack, NextCloud, etc.)

Each app has it's own container.

How's the performance doing it that way?

black3dynamite

@penguinwrangler said in Securing BootStack behind a Ubuntu NGINX Reverse Proxy:

Is the title suppose to be:
"Securing BootStack behind a Ubuntu NGINX Reverse Proxy"

Or was it suppose to be:
"Securing BookStack behind a Ubuntu NGINX Reverse Proxy"

?

BookStack.

Alex Sage

@black3dynamite Excellent from what I can tell.

I don't restrict the containers at all, just lets them use whatever resources they need.

Alex Sage

I want to try setting up a salt master in a container, then having it setup the containers for me

scottalanmiller

@black3dynamite said in Securing BookStack behind a Ubuntu NGINX Reverse Proxy:

@aaronstuder said in Securing BootStack behind a Ubuntu NGINX Reverse Proxy:

This setup is a LXC host, running both NGINX and BookStack in a different containers.

I forward 80/443 from the host to the NGINX container.

Then setup NGINX to reverse proxy to another container (BookStack, NextCloud, etc.)

Each app has it's own container.

How's the performance doing it that way?

LXC has essentially zero overhead. Should act exactly like doing them on the same box.