-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joplin Exporter is not working #9197
Comments
It is working as expected. The warning message informs you it cannot reach a Joplin server on the specified ip/port. Remember that you need to setup port forwarding each time you need, following https://github.com/koreader/koreader/wiki/Joplin#port-forwarding |
The server is working fine. I have setup a personal joplin server and hitting its
I believe, the logic at line 306 in joplin.lua is getting triggered incorrectly due to some reason.
|
@ankitmundada: that's great! I've tried to push an annotation against your server (obviously without a valid token). It served me to catch a bug but is not related with your issue. And the logs provide a bit more info:
If I do the same agaisnt my own instance (with a valid token this time) I have no problems to export to joplin. Please check your device's network connectivity. |
Issue
Joplin Export plugin does not work
Steps to reproduce
I've tried exporting notes from the latest koreader update by setting appropriate config of joplin (ip, port & token). It was working properly in the previous build but the latest update has some issues.
crash.log
(if applicable)crash.log
is a file that is automatically created when KOReader crashes. It cannormally be found in the KOReader directory:
Relevant portion from crash.log
crash.log
The text was updated successfully, but these errors were encountered: