I had few issues while setting things up and would like to share my experience to help other resolve similar issues in future.

Troubleshooting.md

@@ -0,0 +1,29 @@
+## How to get a log
+
+### Docker log
+
+If you're running changedetection.io from the docker, it's as simple as calling this command:  
+`docker logs changedetection.io &> logs.txt`
+
+##  Workaround for 'pyinit_main: can't initialize time' error on Raspberry Pi
+
+When using or installing changedetection.io at the Raspberry Pi device, you can experience these errors:
+- `docker-compose top` or `docker top changedetection.io` do return:  
+`Error response from daemon: Container {CONTAINER_ID} is restarting, wait until the container is running`
+- `docker logs changedetection.io &> logs.txt` produces logs with the following error:  
+`pyinit_main: can't initialize time`
+
+As per https://github.com/linuxserver/docker-papermerge/issues/4, run these commands to workaround this problem:
+`wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb`
+`sudo dpkg -i libseccomp2_2.5.1-1_armhf.deb`
+
+## No Notifications
+
+Make sure you're not sending too long messages, as some notification targets do have message length limitations.  
+For example, too long notification message submitted to the Telegram will produce the following error in the log file:
+
+`WARNING:apprise:Failed to send Telegram notification to 196289410: Bad Request: message is too long, error=400.`  
+`DEBUG:apprise:Response Details:`  
+`b'{"ok":false,"error_code":400,"description":"Bad Request: message is too long"}'`
+
+You can easily get out of length limitations is you're including `{current_snapshot}` into the Notification Body.