From 32d36a56a9dc175137ca6639f6c13334230e35f3 Mon Sep 17 00:00:00 2001 From: Thomas Zarebczan Date: Fri, 8 Jun 2018 17:15:22 -0400 Subject: [PATCH] wallet message --- content/faq/startup-troubleshooting.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/faq/startup-troubleshooting.md b/content/faq/startup-troubleshooting.md index a82a689f..6a761cd1 100644 --- a/content/faq/startup-troubleshooting.md +++ b/content/faq/startup-troubleshooting.md @@ -4,6 +4,8 @@ category: troubleshooting 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). 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.