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

add anchor

Browse source
This commit is contained in:
Thomas Zarebczan 2017-12-22 20:01:06 -05:00 • committed by GitHub
parent 9ac4847741
commit 9fbc5e8d65
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -8,6 +8,7 @@ Proper network connectivity, visibility, and access is a necessity for usage of
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.
If you are having issues syncing to the blockchain, please see [Stuck at blockchain sync](#sync).
### Connectivity and ports
LBRY operates on a couple different ports and if there are conflicts/firewall rules/security settings that prevent them from being utilized, the app/daemon will experience start-up issues. LBRY tries to employ port forwarding through the use of UPnP, which may be disabled on some routers. Either UPnP must be enabled or you have to manually forward the ports below (3333 TCP and 4444 UDP) in order to fully take advantage of the LBRY network. Only 1 PC on a network can have an open outside port, so if you are running multiple PCs with LBRY, they will need to be configured manually.
@ -30,7 +31,7 @@ First and foremost, please ensure you are on the [latest version](https://lbry.i
- Other typical startup troubleshooting would be to ensure that LBRY or lbrynet-daemon is not already running in the background. If the processes cannot be killed, a restart of your computer may be required.
### Known startup issues and workarounds
#### Stuck at blockchain sync
#### Stuck at blockchain sync {#sync}
If you are stuck on the blockchain sync step or it shows a block count that doesn't decrease, you may need to clear your your blockchain cache. To do so, Shut LBRY down completely (check for running LBRY/lbrynet-daemon processes), delete the `blockchain_headers` file in the [lbryum folder](https://lbry.io/faq/lbry-directories) and then start LBRY again.
#### Linux auth_token requirements
Currently, LBRY requires an authorization token to be generated using the [keytar](https://github.com/atom/node-keytar) libraries. Please ensure libsecret and keytar are installed. On some distributions, LBRY won't run unless gnome keyring is also installed/operational. See [GitHub issue](https://github.com/lbryio/lbry-app/issues/386) for more information. If you get a GLIBCXX_3.4.2 error, please see [this issue](https://github.com/lbryio/lbry-app/issues/423#issuecomment-327519486).