Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plex GarminSdkError::-400 #85

Closed
lucasartori opened this issue Nov 23, 2023 · 9 comments
Closed

Plex GarminSdkError::-400 #85

lucasartori opened this issue Nov 23, 2023 · 9 comments
Labels
needs info This issue did not provide enough information to reproduce stale This issue is surpassed by new app versions

Comments

@lucasartori
Copy link

lucasartori commented Nov 23, 2023

GarminSdkError::-400 INVALID_HTTP_BODY_IN_NETWORK_RESPONSE

I get this error testing the server or fetching playlists.

Configuration
Server Address: https://<mydomain>.duckdns.org/ (configured nginx reverse proxy and Let's Encrypt certificate)
Username: PlexEmailAddress
API key: MyPlexToken

Testing with https://<mydomain>.duckdns.org/?X-Plex-Token=<MyPlexToken> works correctly

All other options give 300 (with different domain and/or with port forwarding)

Plex version is 1.32.7.7621
The watch is Fenix 7 Pro Solar

@lucasartori lucasartori changed the title Ples GarminSdkError::-400 Plex GarminSdkError::-400 Nov 23, 2023
@memen45
Copy link
Owner

memen45 commented Nov 23, 2023

Did you try without the trailing slash?

@lucasartori
Copy link
Author

lucasartori commented Nov 24, 2023

After removing the trailing slash from the address it connects but there are still problems

"Test Server" starts but does not complete; appears on the screen

  • Inlog OK
  • No podcasts
    and remains still without proceeding further

Playlist browser works

Selecting playlists to sync works and I select a playlist with only 1 song

When launching synchronization it remains at 0% and "GarminSdkError::0" is displayed

Probably same problem as #84 ?

@memen45
Copy link
Owner

memen45 commented Nov 24, 2023

Plex doesn't have podcasts, so Test server is correct. The error during sync is most likely related to the SSL ciphers you have enabled on the server. See #42.

@lucasartori
Copy link
Author

lucasartori commented Nov 28, 2023

Even after changing the SSL ciphers like in #42 I still get the same "GarminSdkError::0" is displayed

image

@memen45
Copy link
Owner

memen45 commented Jul 30, 2024

Were you able to resolve this or is this still an issue for you?

@memen45 memen45 added stale This issue is surpassed by new app versions needs info This issue did not provide enough information to reproduce labels Jul 30, 2024
@lucasartori
Copy link
Author

I haven't been able to resolve it, it still fails.

@memen45
Copy link
Owner

memen45 commented Jul 30, 2024

Are you able to complete the connection with the SubMusic for Plex app? You can test the Plex connection without any payment. Also you can send debug info from the Settings => Plex => Servers => (Server Name) => Send Debug Info.

Do you happen to have any server logs?

The server address should be reachable from the wifi network that your watch connects to as well. During the Test Server option, the phone connection is still used, but during sync, the wifi network of the watch itself is used instead. You might have an issue with local vs remote Plex url which changes depending on whether your phone is connected or wifi.

@memen45
Copy link
Owner

memen45 commented Aug 23, 2024

Check #71 and #99, make sure to use --key-type rsa with the certbot command. Fenix 7 series does not support other certificates than RSA at the moment, and based on the enabled ciphers you sent, there is only ECDSA enabled.

Did you manually change the certificates or is the Plex default certificate not working?

@memen45
Copy link
Owner

memen45 commented Aug 29, 2024

Closing because of lack of information. If there are updates, feel free to comment or reopen!

@memen45 memen45 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info This issue did not provide enough information to reproduce stale This issue is surpassed by new app versions
Projects
None yet
Development

No branches or pull requests

2 participants