Gateway-mt (multi tenant) is S3-compatible gateway, design to serve multiple users from multiple satellites, and because data is decrypt right here on gateway, it can read data unencrypted, so trust matter here.
Minimum useful command
gateway-mt run \
--auth.base-url='https://auth.storjshare.io' \
--auth.token=123456 \ # set to the same value with edge authservice
--cert-dir='/var/lib/caddy/.local/share/caddy/certificates/acme-v02.api.letsencrypt.org-directory/gateway.example.com' \
--startup-check.satellites='https://www.storj.io/dcs-satellites' \
--insecure-disable-tls=false
When you use --startup-check.satellites. If your satellite config wrong (for example: api having tls on port 7777), the check will stuck forever at this step:
INFO startupcheck/startupcheck.go:45 checking "<sat_address>"
# will stuck at checking satellite step forever..
INFO httpserver/server.go:320 HTTP server started {"addr": "[::]:20010"}
INFO httpserver/server.go:320 HTTPS server started {"addr": "[::]:20011"}
Also, notice that gateway.storjshare.io open on port 443.
If you terminate tls on 443 (https → http), proxy it to 20010, eg: https://gateway.storjshare.io:443.
If you are using haproxy (tcp forward), then forward it to 20011, eg: https://gateway.storjshare.io:20011.
See you on part 16.