4.2 KiB
+++ title = "Reverse Proxy" weight = 50 +++
Reverse Proxy
This contains examples for how to use docspell behind a reverse proxy.
For the examples below, assume the following:
- Docspell app is available at
192.168.1.11:7880
. If it is running on the same machine as the reverse proxy server, you can setlocalhost:7880
instead. - The external domain/hostname is
docspell.example.com
Configuring Docspell
These settings require a complement config part in the docspell configuration file:
-
First, if Docspell REST server is on a different machine, you need to change the
bind.address
setting to be either0.0.0.0
or the ip address of the network interface that the reverse proxy server connects to.docspell.server { # Where the server binds to. bind { address = "192.168.1.11" port = 7880 } }
Note that a value of
0.0.0.0
instead of192.168.1.11
will bind the server to every network interface. -
(Optional) Docspell needs to know the external url. The
base-url
setting should point to the external address. Using above values, it would behttps://docspell.example.com
.docspell.server { # This is the base URL this application is deployed to. This is used # to create absolute URLs and to configure the cookie. base-url = "https://docspell.example.com" ... }
You can also leave the default settings (
localhost
), in this case Docspell uses the request header to determine the external url.
Note that this example assumes that the docspell-joex component is on the same machine. This page is only related for exposing the REST server and web application.
If you have examples for more http servers (e.g. apache), please let me know or add it to this site.
Headers
If base-url
is left to its default, then Docspell tries to find the
external URL from the http request. When using a reverse proxy, you
then need to pass some information from the original request so
Docspell can construct the correct url. These headers are evaluated:
X-Forwarded-Host
X-Forwarded-Proto
X-Forwarded-Port
X-Forwarded-For
Example for nginx:
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port 443;
proxy_set_header X-Forwarded-Proto https;
Nginx
This defines two servers: one listens for http traffic and redirects
to the https variant. Additionally it defines the let's encrypt
.well-known
folder name.
The https server endpoint is configured with the let's encrypt
certificates and acts as a proxy for the application at
192.168.1.11:7880
.
server {
listen 0.0.0.0:80 ;
listen [::]:80 ;
server_name docspell.example.com ;
location /.well-known/acme-challenge {
root /var/data/nginx/ACME-PUBLIC;
auth_basic off;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 0.0.0.0:443 ssl http2 ;
listen [::]:443 ssl http2 ;
server_name docspell.example.com ;
location /.well-known/acme-challenge {
root /var/data/nginx/ACME-PUBLIC;
auth_basic off;
}
ssl_certificate /var/lib/acme/docspell.example.com/fullchain.pem;
ssl_certificate_key /var/lib/acme/docspell.example.com/key.pem;
ssl_trusted_certificate /var/lib/acme/docspell.example.com/full.pem;
location / {
proxy_pass http://192.168.1.11:7880;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port 443;
proxy_set_header X-Forwarded-Proto https;
//client_max_body_size 40M; //to allow larger uploads
}
}
Caddy
docspell.example.com {
reverse_proxy http://192.168.1.11:7880
}
Traefik 2
http:
routers:
docspell:
rule: "Host(`docspell.example.com`)"
service: docspell
entryPoints:
- web-secure # or whatever you named it for SSL
services:
docspell:
loadBalancer:
servers:
- url: http://192.168.1.11:7880 # the ip of the container, localhost if you use docker port mapping
healthCheck:
path: /api/info/version