LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-08-23 17:47:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

remove message

Browse source
This commit is contained in:
Thomas Zarebczan 2018-06-08 17:38:54 -04:00 • committed by GitHub
parent 32d36a56a9
commit dedc0e8235
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/faq/startup-troubleshooting.md
View file

@ -4,8 +4,6 @@ category: troubleshooting
order: 1 order: 1
--- ---
# **Our wallet servers are currently down and we are working to get them back up ASAP, thanks for your patience. Please try opening the app again in a couple hours**
Proper network connectivity, visibility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer [one-on-one troubleshooting](https://lbry.io/faq/how-to-report-bugs). Proper network connectivity, visibility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer [one-on-one troubleshooting](https://lbry.io/faq/how-to-report-bugs).
The first area to check for start-up issues is the [LBRY log file](https://lbry.io/faq/how-to-find-lbry-log-file). Except in extreme cases, a log file should be generated by the daemon startup process and will usually reveal clues on where to find problems. The first area to check for start-up issues is the [LBRY log file](https://lbry.io/faq/how-to-find-lbry-log-file). Except in extreme cases, a log file should be generated by the daemon startup process and will usually reveal clues on where to find problems.