api problem #7
Description
Bug Report: Kimai API Integration Issue
Title: Code Timer fails to connect to Kimai 2 API with Bearer Token authentication
Description:
Code Timer is unable to establish a connection to a Kimai 2 instance despite the API being fully functional and accessible via web browser and curl.
Environment:
Kimai Version: 2.19.1
Device: Android (model not specified)
Code Timer Version: [Latest / specify version]
Network: Tailscale VPN (self-hosted, remote access)
Issue Details:
When attempting to connect to a Kimai instance at a custom domain with:
URL: https://[custom-domain].ts.net
API Token: [valid Bearer token]
The application displays: "Connection is invalid"
What Works:
✅ Direct browser access: https://[custom-domain].ts.net → Kimai UI loads and functions correctly
✅ curl command with Bearer token authentication:
bash
curl -H "Authorization: Bearer "
https://[custom-domain].ts.net/api/version
Returns: HTTP/1.1 200 OK with valid API response {"version":"2.19.1",...}
✅ Official Kimai Mobile app connects successfully with the same credentials
What Doesn't Work:
❌ Code Timer: Always returns "Connection is invalid"
❌ Tested URL variations: with/without trailing slash, with /api suffix
Technical Details:
SSL/TLS: Valid Let's Encrypt certificate, TLS 1.3, certificate chain complete
API Authentication: Kimai uses Authorization: Bearer (not X-API-TOKEN)
Network connectivity: No issues (browser and other apps work)
Expected Behavior:
Code Timer should successfully connect to the Kimai API and authenticate using the Bearer token.
Actual Behavior:
Connection fails with generic "Connection is invalid" error message (no detailed error log visible to user).
Suggestion:
Please verify:
Whether Code Timer properly handles Authorization: Bearer header format
If there are any specific URL format requirements
Consider adding debug logging for connection errors