LBRY app error on startup: Wallet server took a bit too long to respond

[Sessh22]

LBRY app error on startup: Wallet server took a bit too long to respond

[amaloy]

I'm getting the same on Linux.

[keikari]

That happens with default hub servers having issues.
If it happens again, you could try to connect to Odysee hub, or some other hub.
You can do that by adding something like this in your daemon_settings.yml https://lbry.tech/resources/daemon-settings

lbryum_servers:
  - a-hub1.odysee.com:50001

(Hub servers index the metadata from blockchain in a database that can be queried. https://github.com/lbryio/hub)

[Sessh22]

As I stated in the OP as to how this problem "fixes itself", it once again resolved itself spontaneously later on in the evening which put it at around a full day of not being able to start up under these conditions. I am just wondering if this is a LBRY issue that can be fixed or if it's a server issue and out of the scope of what can be fixed in the app.

Glad to know it's not just me though.

[Sessh22]

Cool so I just made a backup of the original daemon_settings.yml file and added this line to the one in use:

lbryum_servers: ['spv11.lbry.com:50001','spv19.lbry.com:50001','a-hub1.odysee.com:50001']

I restarted LBRY with this line in there and it still started up fine. I didn't know if I had to include the two default servers in there or not as I didn't want to override the defaults by using only the odysee one. If I only have the odysee one in this file, does it just include it with the two default servers or does it prioritize this entry?

[keikari]

Not sure how it selects. But if you prefer to use default servers, you can just remove or comment out that line completely. Generally default servers should be up, so rarely need to handle hubs manually.

[Sessh22]

Ok. I suppose I will just leave it as it is now with three servers (including the two defaults) manually added and see if this happens again. I'll close this issue, but at least there's a solution here to try for anyone else having this issue from time to time.