You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note - usually a single line of log is not sufficient. The lines just before the error occurs can give useful context and greatly assist with debugging.
There is a built-in debug log creator on the logs page which makes it easy to provide this information
To use it, first go to the log page and make sure debug logging is OFF
Now press the "Start debug log" button
Go and do whatever you need to recreate the error
Go back to the log page and press "Save debug log"
You can now turn debug logging off again if you want
The saved log file will be found in your lazylibrarian log directory called debug.zip
It will contain all lines logged since you pressed "Start debug log" with any passwords and api keys removed
Attach the zip file to your bug report.
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to use apprise to send notifications from lazy librarian. This is the config in http://myserver/config:
I am getting the following error when I click on [Test]
And, nothing is logged.
The apprise configuration is working. This is a screenshot from the lazy librarian docker container:
And of course, this time the apprise message arrives (to telegram, this time).
LazyLibrarian version number
Current Version: 997c11e4
Operating system used
Linux
Interface in use
Default, I believe... not sure if it is relevant for this error
Which api
Google Books
Source of your LazyLibrarian installation
Docker image linuxserver/lazylibrarian
Relevant debug log with api keys and any passwords redacted
Full logs from docker:
Please note - usually a single line of log is not sufficient. The lines just before the error occurs can give useful context and greatly assist with debugging.
There is a built-in debug log creator on the logs page which makes it easy to provide this information
The text was updated successfully, but these errors were encountered: