[Bug] Liner shows an error screen on launch (HTTP 503) #35
Replies: 2 comments 1 reply
Additional issue: Unable to play a trackI also encountered an issue when trying to play the following track: Actual behavior: Liner displays the error message Expected behavior: The track should play normally if it is available. I'm not sure whether this issue is related to the API errors described above, but I wanted to report it as well. |
0 replies
|
Fixed, download last version. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Liner shows an error screen on launch
I encountered the following error screen when trying to open Liner:
Diagnostic report
Environment
dev@liner/client/0.1.35en-US2026-10-16 02:13:23 UTCSummary
The diagnostic report indicates that the application can connect to Liner's services, but requests to the main API are failing with HTTP 503 (Service Unavailable).
HTTP 503)Affected API endpoints
The following requests returned HTTP 503:
GET /v1/meGET /v1/me/playlistsGET /v1/me/library/tracksGET /v1/me/recommendations/daily-mixesGET /v1/me/historyGET /v1/explore/popularThe failed requests took approximately 5.3–5.4 seconds each.
Expected behavior
Liner should launch normally and load the main interface.
Actual behavior
Liner displays an error screen during startup, preventing me from accessing the application normally.
Additional notes
The diagnostic checks suggest that DNS resolution, TCP connectivity, and TLS negotiation are working. However, the main API consistently returns HTTP 503 across multiple endpoints.
This may indicate a temporary API-side availability issue, although further investigation is needed to identify the exact cause.
Could you please investigate this issue?
Thank you!
All reactions