Long passwords issue?

[NipponBill]

Might there be an issue with long passwords in this plugin like the Rumble plugin? I have a 50+ character password for Odysee/LBRY and this plugin gives me an error when trying to start it.

When trying to start LBRY+ I get this error in my log:

I also have the old original LBRY plugin installed.

[azzy9]

Odysee login is different and doesn't require the password to be hashed when submitted like rumble.
I have tested it with a 64 character password and worked fine, so password length is not an issue.
I also tried with symbols just in case and worked fine.
Again my handling of what Odysee considers incorrect is not the best.

Edit: just thought I would add, the original LBRY plugin should not conflict with this plugin at all since they use different plugin IDs

[NipponBill]

@azzy9 Thanks for confirming that, about the password length.

Do you think this PythonToCppException error in my log, or the Unverified HTTPS request to 'api.odysee.com' might be something that could be worked around? I can't start the app at all due to this error.

Again, I'm on a (fairly) fresh install of LibreElec 11.03 with Kodi 20.2

[azzy9]

The certificate error is not an issue as mine does it and works fine.
The second error is the issue and is actually thrown by the code, which is what I mean to handle it better rather than throw the error.

The error is thrown here:
https://github.com/azzy9/plugin.video.lbryplus/blob/master/resources/lib/external.py#L183

This will throw an error if the login method returns false here:
https://github.com/azzy9/plugin.video.lbryplus/blob/master/resources/lib/odysee.py#L88

The most likely scenario is that Odysee doesn't like your details for some reason, so the method is returning false.
I should most probably create a login test method like in rumble.

[azzy9]

Hi @NipponBill,
could you try the login test setting in v0.6.0

[NipponBill]

@azzy9 I can now access the app.
Recent and Live Streams are populated, but with general content.

Test Login Details shows:

Login failed - Incorrect details
Unable to get Auth Token from Odysee.com

Log files only show the Unverified HTTPS request to 'api.odysee.com' reported before.

[azzy9]

@NipponBill, I had removed the part of code that throws the error.

Unable to get Auth Token from Odysee.com

It usually show this if you try the test multiple times as it doesn't like to get flooded with login requests within a short period of time.

Login failed - Incorrect details

This is the final stage of login, when Odysee doesn't like your password.
There is a username check before this, so it is passing that.
Either the password is incorrect, or there maybe some other reason it doesn't like your password. e.g. maybe there is some weird characters?

Note: I have tested passwords with symbols previously with no issue.

[NipponBill]

@azzy9 I changed my mixed character password to a passphrase that only contains letters and hyphens. Even that didn't work. I get the same errors.

Here's a photo of the log:

Looks like there's an error involving connectionpool.py ... but that existed in the original error...

[azzy9]

The cert error is not an issue. if it gets to the login failed in the test, that means the requests are getting through fine since it has to make a couple of requests before that, (get auth token & check if email exists for login). it just has them errors to make you aware that the connection is not verified via the cert.
I'm not sure what more I can suggest for this

[azzy9]

Could you update to v0.6.1 & do the login test again.
In this version, when it gets to "login failed - incorrect login details" it will put the error that is received from Odysee itself into the log so we should be able to see what Odysee thinks the error is.
It should begin with the text below in the log

LBRY+ Login Fail >

[NipponBill]

@azzy9 with v0.6.1 in the log I get:

Incorrect email and/or password

So I created a brand new account for testing with a very short, uncomplex password, and I get the same error.

I did some more testing. I disabled Odysee login in the settings and tried to view videos from Recent. Every one I try results in a API error popup.

API Error
Claim release time is in the future., not ready to be viewed yet

This happens for every video in the Recent list, whether logged in or not.

The log doesn't seem to show much:

[azzy9]

Sorry, I am at lost at what to suggest since it is Odysee returning that the details are incorrect.

Would it be possible to inform me of the Kodi version and device OS e.g. android

Some basic things I can suggest to check.

• Make sure account's is activated
• check if email has weird characters that cause email e.g. + sign (but shouldn't be an issue since it is passing the user exists check)
• Compare with browsers requests to see if details are submitted to https://api.odysee.com, make be different based upon region, it shouldn't be an issue but you never know
• You could try using a VPN and see if that has any effect (shouldn't if you can log in via browser)
• You could try messing with time zones see if that helps (I have messed around with it but didn't help, but again you never know)

Sorry to say, but I am grasping at straws as I am not sure how to progress from here.

[NipponBill]

Would it be possible to inform me of the Kodi version and device OS e.g. android

It's an install of LibreElec 11.03 with Kodi 20.2 on a Raspberry Pi 4 with 8GB RAM.

• The account is activated, one account has been used for years
• mails used for signup aren't using + or other special characters
• I only use Odysee with a VPN. I've tried different exit nodes and different vendors. No change.
• I haven't been able to figure out time-zone manipulation in LibreElec

I appreciate all you help on this. I'm stumped as well.

[noticons]

It is possible you are using characters that, while acceptable to Odysee, cause other apps, like lbry.plus to stumble.
Try generating a password without the following characters:
&#@~$%

[NipponBill]

It is possible you are using characters that, while acceptable to Odysee, cause other apps, like lbry.plus to stumble.
Try generating a password without the following characters:
&#@~$%

See above:

I changed my mixed character password to a passphrase that only contains letters and hyphens. Even that didn't work.