v0.2.7 - Plex Connection Fix
Bug Fixes
Plex Connection Issues
Fixed 400 Bad Request errors that occurred when connecting to Plex servers. This issue commonly affected users when:
- Plex tokens had extra whitespace (from copy-paste)
- Server required HTTPS connections
- Token formatting was incorrect
New Features
Connection Testing Command
plexmix config test- Diagnose Plex server connection problems- Shows server URL and token details
- Tests connection and library access
- Provides troubleshooting guidance
Improvements
Enhanced Error Handling
- Auto-strip whitespace from Plex tokens
- Specific
BadRequestexception handling - Detailed error messages with root cause explanations
- Show token length and server URL in diagnostics
Better User Experience
- Improved error messages in
config initwith step-by-step troubleshooting - Clear guidance on http vs https requirements
- Common server URL examples provided
- Helpful tips displayed on connection failure
Commands
# Test your Plex connection
plexmix config test
# Re-run setup with improved error handling
plexmix config initTroubleshooting 400 Bad Request Errors
If you previously encountered connection issues:
- Try again - Whitespace is now automatically stripped from tokens
- Use HTTPS - Try
https://instead ofhttp://for your server URL - Test connection - Run
plexmix config testto diagnose - Verify token - Ensure no extra characters when copying from Plex
- Check port - Default is 32400, verify your server uses this
Documentation
- Added troubleshooting section to README for connection issues
- Documented common Plex server URL formats (
http://localhost:32400,https://server:32400, etc.) - Added guidance for diagnosing connection problems
Files Changed
src/plexmix/plex/client.py- Enhanced connection handling and error messagessrc/plexmix/cli/main.py- Added config test command, improved init error messagesREADME.md- Added troubleshooting guide for Plex connections
Testing
All 91 tests passing ✅