remove startup failure reason

This commit is contained in:
Thomas Zarebczan 2018-02-08 11:51:07 -05:00 committed by GitHub
parent bdeac18ad2
commit 075d7bbc78
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -4,7 +4,7 @@ category: troubleshooting
order: 1
---
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.
@ -25,7 +25,6 @@ LBRY operates on a couple different ports and if there are conflicts/firewall ru
### LBRY used to work previously but now it won't start
First and foremost, please ensure you are on the [latest version](https://lbry.io/get) of LBRY. Reinstalling the latest version may alleviate some start-up issues. Before installing, either make sure no LBRY/lbrynet processes or simply reboot your computer.
- On Windows, you may receive an error titled `Uncaught Exception - Error: Object has been destroyed...` which prevents you from starting LBRY. This usually means LBRY.exe or lbrynet-daemon.exe is already running in the background. Check the task manager, kill the process(es) and start LBRY again. Please see this [GitHub issue](https://github.com/lbryio/lbry-app/issues/353) for more details.
- On Windows, you may receive an error titled `Uncaught Exception - Error spawn...ENOENT` which usually means LBRY can't find the daemon exe file. Please see this [GitHub issue](https://github.com/lbryio/lbry-app/issues/396) for more details. The workaround is to rerun the [latest](https://lbry.io/get) LBRY installation file.
- On older MAC installations, you may run into an issue with the daemon shutting down immediately. Please see [this GitHub issue](https://github.com/lbryio/lbry-app/issues/291) for troubleshooting.
- 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.