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

add lbrylog.net instructions

Browse source 
Moved email above in app bug report, easier to track.
Added lbrynet.log file instructions.
This commit is contained in:
Thomas Zarebczan 2017-07-14 19:46:36 -04:00 • committed by GitHub
parent 6792d16ce7
commit f845ee9db4
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/faq/how-to-report-bugs.md
View file

@ -3,10 +3,10 @@ title: How do I get help or report a bug?
category: setup
---
For live help or to report a bug, please join [our chat](https://slack.lbry.io) and in the #help channel, post a detailed message with the issue you are experiencing. The more information you can provide, the better we can support!
For live help or to report a bug, please join [our chat](https://slack.lbry.io) and in the #help channel, post a detailed message with the issue you are experiencing. LBRY log files are a good source of information for us, you can [find them here](https://lbry.io/faq/how-to-find-lbry-log-file).
To report a bug via the LBRY App, go to Help from the menu bar and then click the "Submit a Bug Report" button.
You can also send us an email to [help@lbry.io](mailto:help@lbry.io) with the details of your issue or bug report. If it's troubleshooting related, please attach [your LBRY log file](https://lbry.io/faq/how-to-find-lbry-log-file).
You can also [send us an email](mailto:help@lbry.io) with the details of your issue or bug report.
To report a bug via the LBRY App, go to Help from the menu bar and then click the "Submit a Bug Report" button.
If you're a developer or technical, you're welcome to open an issue directly on GitHub - [Daemon related](https://github.com/lbryio/lbry/issues) or [Application related](https://github.com/lbryio/lbry-app/issues). Please do a quick search in both repositories to see if a similar issue already exists.