Joplin Server Edition

Feature
#21

seems its working
image

#22

OK, Iā€™m now seeing the same. Iā€™ve edited the docker-compose.yml above to reflect this.

1 Like
#23

i seem to be getting a certificate error when trying to conenct to the installed instance of joplin server

Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:

request to https://notes.domain.tld/api/sessions failed, reason: certificate has expired (Code CERT_HAS_EXPIRED)

EDIT:
Disccused here: Fix for "Certificate has expired" error with Joplin Cloud and self-hosted sync targets - News - Joplin Forum

#24

Yes, thatā€™s a known bug in Joplin, shown up by the Letā€™s Encrypt change a few weeks back. Itā€™s slated to be fixed in the 2.5 release. For now, you can work around it by telling Joplin not to verify certificates (which compromises security).

1 Like
#25

working perfectly now. i love the ability to publish notes, more than anything.

#26

what could be causing this error, when iexecuting docker-compose up -d
docker.errors.DockerException: Error while fetching server API version: UnixHTTPConnectionPool(host=ā€˜localhostā€™, port=None): Read timed out. (read timeout=60)
[44474] Failed to execute script docker-compose

#27

Is the above command issued automatically after every reboot?

#28

not really, i eleive you should be able to add it permanently to the network