Problem: When launching the Shadow server, the following error occurs:
expected <block end>, but found BlockMappingStart
Solution: Tabulation within equal-rank groupings in shadow.yml must be the same for all items.
***
Problem: Shadow client update notifications are not received in Android.
Solution: Disable Google Play Protect for non-Google-Play applications (Settings -> Google -> Security -> Google Play Protect -> Settings -> Scan apps with Play Protect).
***
Problem: A package error occurs during the Shadow client update.
Solution: Enable installation from unknown sources for Shadow (Settings -> Apps & Notifications -> App info -> Shadow -> Install unknown apps).
***
Problem: During the initial provisioning of the Shadow client the “Error obtaining the server certificate” error is displayed after scanning the registration QR code.
Solution: This error means that there is some basic communication problem preventing the client from accessing the server, hence any advanced troubleshooting is pointless at this stage. The most common reasons for this error are:
- the Shadow server is not running (check the Shadow service status and the console output/logs in case it is exited, also double check shadow.p12 and cacerts passwords and whether the Shadow server certificate is present in cacerts)
- there is no Internet connectivity on the smartphone (zero balance or no coverage)
- the Shadow server port is closed or improperly forwarded on the firewall
- the Shadow server URL in the QR code is incorrect (check whether you supplied the proper port number when generating the code)
***
Problem: Attachments are not being sent while simple messages are served correctly.
Solution: This problem may be caused by some malfunction or misconfiguration of Minio, but the first thing to be checked is the serviceConfiguration:cloudUri parameter of the Shadow configuration file. It should be set to the Minio URL as accessible from the Internet.