- Access your DNS provider's control panel (Cloudflare, Namecheap, GoDaddy, etc.)
- Create DNS record:
- Type: A
- Name: plex (or your subdomain)
- Content: YOUR_SERVER_IP
- TTL: Automatic or 3600
- If using Cloudflare: Set to DNS only (Gray cloud)
Update your .env file:
PLEX_HOST=plex.yourdomain.com-
SSL/TLS:
- Plex handles its own SSL certificates
- No additional SSL configuration needed
- If using Cloudflare, set SSL/TLS encryption mode to "Full"
-
DNS Provider Settings:
- Do not enable proxy/CDN features for Plex
- Direct connection is required for optimal performance
-
DNS Propagation:
# Check if DNS is resolving dig plex.yourdomain.com # Test connection curl -I https://plex.yourdomain.com:32400/web
-
Plex Connection:
- Open https://plex.yourdomain.com:32400/web
- Check Settings -> Remote Access
- Verify "Fully accessible outside your network"
-
SSL Certificate:
- Click the padlock in your browser
- Verify certificate is issued by Plex
-
DNS Not Resolving:
# Check DNS propagation dig plex.yourdomain.com # Check from different location nslookup plex.yourdomain.com 8.8.8.8
-
Cannot Access Plex:
- Verify firewall allows port 32400
# Check firewall status ufw status # Test port connectivity nc -zv plex.yourdomain.com 32400
-
SSL Certificate Issues:
- Clear browser cache
- Wait up to 15 minutes for Plex to issue certificate
- Verify PLEX_HOST is correct in .env
-
Remote Access Issues:
- Check Plex Settings -> Remote Access
- Verify no proxy/CDN is between server and internet
- Test direct IP access first: http://YOUR_SERVER_IP:32400/web
-
Domain Issues:
# Restart Plex container docker-compose restart plex # Check logs docker-compose logs plex
-
Reset DNS Cache:
# On macOS sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder # On Linux sudo systemd-resolve --flush-caches
- Use a dedicated subdomain for Plex
- Allow direct connections (no proxy)
- Keep DNS TTL low during initial setup
- Document your DNS settings
Need more help? Check TROUBLESHOOTING.md for general issues.