Support
Two routes, depending on what you need.
Getting in touch
Bugs and feature requests
GitHub Issues is the preferred route. It is public, searchable, and someone else may already have hit it.
Open an issueEverything else
Account, privacy questions, or anything you would rather not post in public.
support@latchbabybuddy.app“The QR scan says my connection is not encrypted, but my server is HTTPS”
This is almost always a reverse proxy - nginx, Caddy, Traefik, Nginx Proxy Manager - terminating HTTPS and forwarding plain HTTP to Baby Buddy. Baby Buddy builds the QR code from the address it sees, which is http://, so the code tells Latch to connect unencrypted. iOS refuses, and pairing stops. Nothing insecure happens; the connection simply never opens.
Get going now
On the scan screen tap Enter details manually, type your server address (baby.example.com - no scheme needed, Latch defaults to HTTPS), paste the API token from the same Add a Device page, and connect.
Fix it properly
Make the proxy send X-Forwarded-Proto, and set SECURE_PROXY_SSL_HEADER=True on Baby Buddy so it trusts that header. After recreating the container the QR code carries https:// and scanning works. Full instructions, including the CSRF_TRUSTED_ORIGINS setting and the hostname caveat, are in the FAQ:
Read the full fix in docs/faq.md
Questions about Baby Buddy itself
Latch is an unofficial client. For anything about installing, hosting, upgrading or configuring Baby Buddy, the project itself is the right place to ask - we are not their support desk, and they will answer better than we can.