You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server seems to suddenly be down for multiple people. The desktop app shows this:
Error starting up
You can try refreshing to fix it. If you still have issues, your anti-virus software or firewall may be preventing startup.
Reach out to [email protected] for help, or check out this link
Is this a planned outage or something else?
The text was updated successfully, but these errors were encountered:
I am seeing this issue as well recent days, LBRY_0.53.9.AppImage .
I was trying to restore ~/.config/LBRY from backups (for one backup it worked, but i think it was coincidence since now not working for any backup).
lbrynet.log shows: failed to connect to any spv servers, retrying later Full log here for context.
One of the lbry server IP that LBRY unable to connect is up for me (yet port is closed - server app is not running?, not filtered?):
$ nmap 212.102.60.88 -p 50001
Nmap scan report for unn-212-102-60-88.cdn77.com (212.102.60.88)
Host is up (0.14s latency).
PORT STATE SERVICE
50001/tcp closed unknown
It started working. Their servers was down apparently. "The LBRY app is a graphical browser for the decentralized content marketplace provided by the LBRY protocol." so the access to the decentralized content marketplace is centralized around LBRY browser servers?
Some tips regarding custom wallet server setup and setting it as a CLI parameter: lbryio/lbry-sdk#2213
Btw. one can also set wallet server via GUI, settings. I do not know the l!st of servers.
The server seems to suddenly be down for multiple people. The desktop app shows this:
Error starting up
You can try refreshing to fix it. If you still have issues, your anti-virus software or firewall may be preventing startup.
Reach out to [email protected] for help, or check out
this link
Is this a planned outage or something else?
The text was updated successfully, but these errors were encountered: