⛩️Reverse Proxies

Running a reverse proxy in front of sqliterg is almost mandatory if you want to expose it on the internet. More than that, there are a number of reverse proxies that allow you to protect a http connection with https, using a free certificate provided for example by Let's Encrypt or similar.

Read more here.

We'll show here how to integrate with two popular solutions, caddy and NGINX.

Caddy

To access sqliterg from https://sqlite.mydomain.com:

1. Expose ports 80 and 443 of the server to which the DNS points;

2. Run sqliterg. Leave the port as 12321;

3. Launch caddy:

caddy reverse-proxy --from sqlite.mydomain.com --to localhost:12321

You'll need to launch caddy with root/admin privileges, as it must access privileged ports.

NGINX

NGINX is quite complex to configure, and its configuration is beyond the scope of this document. Usually, we make use of LinuxServer's Swag Docker image, paired with sqliterg's own docker image. The relevant config is in nginx/site-confs/default:

server {
        listen 443 ssl http2;
        server_name sqlite.mydomain.com;
        include /config/nginx/proxy-confs/*.subfolder.conf;
        include /config/nginx/ssl.conf;
        location / {
                proxy_pass http://localhost:12321/;
        }
}