Troubleshooting
Having issues with HD Homey? This guide covers common problems and their solutions.
Quick Diagnostics
Before diving into specific issues, check these basics:
Check container/process status:
bashdocker ps # If using Docker # or systemctl status hd-homey # If using systemdView logs:
bashdocker logs hd-homey # Docker # or journalctl -u hd-homey # systemdVerify environment variables:
bashdocker exec hd-homey env | grep HD_HOMEYTest network connectivity:
bash# From HD Homey container to HDHomeRun device docker exec hd-homey curl http://YOUR_HDHR_IP/discover.json
Common Issues
Authentication Problems
Can't log in / Authentication loops
Symptoms: Login page keeps reloading, or "Unauthorized" errors
Solutions:
- Verify
AUTH_SECRETis set and consistent across restarts - Clear browser cookies for the site
- Check that
BETTER_AUTH_URLmatches your access URL (or leave blank for auto-detection) - Ensure system time is correct (JWT tokens are time-sensitive)
# Verify AUTH_SECRET is set
docker exec hd-homey env | grep AUTH_SECRET
# Regenerate if needed
openssl rand -base64 32"Forbidden" or "Unauthorized" errors
Symptoms: Can access some pages but not others
Solutions:
- Check user role (admin vs viewer)
- Verify session hasn't expired
- Refresh the page to update session
- Re-login to create fresh session
Streaming Issues
Streams won't play
Symptoms: Video player shows error or infinite loading
Solutions:
Check tuner connectivity:
- Go to Tuners page
- Click "Test Connection" on your tuner
- Verify tuner shows green/online status
Verify channel availability:
- Refresh channel lineup
- Check if channel plays on HDHomeRun directly
- Try different channel to isolate issue
Browser codec support:
- Most browsers don't support MPEG-2 natively
- Use transcoded stream (HLS option)
- Or use external player like VLC
Check stream tokens:
- Tokens are time-limited (default 24 hours)
- Regenerate stream URL if expired
- Check
HD_HOMEY_PROXY_HOSTis set correctly (or verify auto-detection works)
Transcoding fails
Symptoms: HLS streams won't start, transcoding errors in logs
Solutions:
Verify FFmpeg is installed:
bashdocker exec hd-homey ffmpeg -versionCheck disk space:
bashdf -h # Transcoded segments need temp storageReview FFmpeg logs:
bashdocker logs hd-homey 2>&1 | grep -i ffmpegIncrease timeout if streams are slow to start:
- Network buffering may need more time
- Check bandwidth between HD Homey and HDHomeRun
Tuner Issues
HDHomeRun device not found
Symptoms: Auto-discovery doesn't find tuner, manual add fails
Solutions:
Check network connectivity:
bash# From HD Homey host ping YOUR_HDHR_IP curl http://YOUR_HDHR_IP/discover.jsonVerify Docker network mode:
- Use
network_mode: hostfor auto-discovery - Or manually add tuner with IP address
- Use
Check firewall rules:
- HDHomeRun uses port 80 for API
- UDP port 65001 for discovery
Verify HDHomeRun is online:
- Check LED on device
- Access web interface at
http://YOUR_HDHR_IP - Restart HDHomeRun device
Channels not updating
Symptoms: Old channels shown, lineup doesn't refresh
Solutions:
Manual refresh:
- Go to Channels page
- Click "Refresh Lineup"
Check tuner configuration:
- Verify tuner is online
- Test connection to tuner
- Check antenna/cable signal
Database issues:
- Check database file permissions
- Verify
HD_HOMEY_DB_PATHparent directory is writable - Review logs for database errors
Database Problems
"Unable to open database" error
Symptoms: Application won't start, database errors in logs
Solutions:
Check file permissions:
bash# Check parent directory of HD_HOMEY_DB_PATH ls -la $(dirname /path/to/hd_homey.db) # Should be writable by HD Homey process userVerify parent directory exists (HD Homey creates it automatically, but check permissions):
bashmkdir -p $(dirname /path/to/hd_homey.db)Check disk space:
bashdf -h /path/toRestore from backup if database is corrupted:
bashcp /path/to/backup/hd_homey.db /path/to/hd_homey.db
Migration failures
Symptoms: App won't start after update, migration errors
Solutions:
Backup database first:
bashcp hd_homey.db hd_homey.db.backupCheck migration logs:
bashdocker logs hd-homey 2>&1 | grep -i migrationManual migration (last resort):
bashdocker exec -it hd-homey npm run db:migrate
Remote Access Issues
Can't access HD Homey remotely
Symptoms: Works on local network, not from internet
Solutions: See detailed guide →
Quick checklist:
- Port forwarding configured (port 3000)
- Firewall allows incoming connections
HD_HOMEY_PROXY_HOSTset to external URL (or verify auto-detection works)AUTH_TRUST_HOST=trueif behind reverse proxy (for auto-detection)- HTTPS recommended for security
Performance Issues
Slow page loads
Symptoms: Web interface is sluggish
Solutions:
Check resource usage:
bashdocker stats hd-homeyReview logs for errors:
bashdocker logs hd-homey --tail 100Increase container resources if needed:
yaml# compose.yml services: hd-homey: deploy: resources: limits: memory: 512M
High CPU usage
Symptoms: CPU consistently high, fans spinning
Solutions:
Check active transcode sessions:
- Multiple users streaming = multiple transcodes
- Consider hardware transcoding (future feature)
Reduce transcode quality:
- Lower bitrate in transcoding settings
- Adjust preset (faster = less CPU, lower quality)
Limit concurrent streams:
- Add message for users about capacity
- Consider upgrading hardware
Still Having Issues?
If your problem isn't covered here:
- Check logs carefully for error messages
- Search GitHub Issues for similar problems
- Create a new issue with:
- HD Homey version
- Installation method (Docker/source)
- Complete error messages
- Steps to reproduce
- Environment details
