https-portal VS selfhosted-apps-docker

HTTPS-PORTAL has everything I need.

If you use LetsEncrypt and Docker, I can recommend HTTPS Portal to automatically manage your SSL certs: https://github.com/SteveLTN/https-portal

I use it for my blog and have never had any issues with certs being renewed well in advance of their expiration date.

This looks awesome!

What I couldn't immediately see from skimming the repo is:

How hard would it be to use a docker-based automatic https proxy such as this [1] with all projects?

I've had a handfull of docker-based services running for many years and love the convenience. What I'm doing now is simply wrap the images in a bash script that stops the containers, snapshots the ZFS volume, pulls newer versions and re-launches everything. That's then run via cron once a day. Zero issues across at least five years.

[1] https://github.com/SteveLTN/https-portal

HTTPS-PORTAL [DockerHub, GitHub]

You're welcome! I might sound "advertise-y" here, but perhaps you can look into Nginx Proxy Manager or Https-Portal as well since they do involve Nginx.

For the nginx reverse proxy I use this https proxy. It sits on top of all my containers, enables and renews https automatically with let’s encrypt and has very good defaults.

You can use https://github.com/SteveLTN/https-portal. You’ll be up and running in 5 minutes.

Heres documentation how I run mine. You need to learn a bit of docker, but its easy.

Heres the way I deployed it in docker using S6 image. Maybe try that if theres a change.

WD=/opt/rustdesk #rm $WD/ -R mkdir -p $WD/{setup,data,web} cd $WD/setup cat << 'EOF' >docker-compose.yaml version: '3.7' #Links #https://hub.docker.com/r/rustdesk/rustdesk-server/tags #https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/docker/ #https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/rustdesk #https://github.com/rustdesk/rustdesk-server#s6-overlay-based-images #https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/relay/ #https://rustdesk.com/docs/en/dev/build/web/ services: rustdesk_server: container_name: rustdesk_server hostname: rustdesk_server image: ${SERVER_IMAGE} # network_mode: host networks: - rustdesk_net ports: - 21115:21115 - 21116:21116 - 21116:21116/udp - 21117:21117 - 21118:21118 - 21119:21119 volumes: - type: bind source: /opt/rustdesk/data/ target: /data environment: - 'TZ=${TZ}' - 'RELAY=${RELAY}' - 'ENCRYPTED_ONLY=${ENCRYPTED_ONLY}' - 'KEY_PUB=${KEY_PUB}' - 'KEY_PRIV=${KEY_PRIV}' rustdesk_web: container_name: rustdesk_web hostname: rustdesk_web image: pmietlicki/rustdesk-web-client:latest # network_mode: host networks: - rustdesk_net ports: - 5000:5000 volumes: #docker cp rustdesk_web:/app . #sed -i -e 's/supportdesk.itportaal.nl/sub.domain.com/g' ./app/build/web/main.dart.js #sed -i -e 's/OvYPJS8I5xV+d6sx3a7Ce9TVakfKdT3Zy3T7C1jjx+A=/PUBKEY/g' ./app/build/web/main.dart.js - type: bind source: /opt/rustdesk/web/app/ target: /app - type: bind source: /opt/rustdesk/data/ target: /root environment: - 'TZ=${TZ}' networks: rustdesk_net: driver: bridge EOF

I tested several reverse proxy setups, the one I like the best is Caddy for its simplicity while being very feature rich. Here is a guide with examples how to setup Caddy. It includes even monitoring who connects from where.

I used plain wireguard on dockerhost for a while, now I am running wg-easy.

This guide could be useful.

Here is some basic setup to get the idea.

This repo should generally be useful, there is speedrun to hosting shit in docker in it...

This is bookstack compose I use.

prometheus + grafana + loki for monitoring, this could help