SOUL 2.15


Certificate authority integration, maintenance updates (stable/90+91) – 31.05.2016

Update stable/90 had been pulled due to loading issues of folders while server is listening to a non-protonet address. Servers already updated are showing “Current version: unknown (unknown)”until being updated again.



Easier deployment of a dynamic domain with automatic certificate creation using Let’s Encrypt

So far setting up a Protonet server with an own internet domain was difficult, when it came to the steps to buy the correct certificate and put it in the right format and place.

Using the new console script “letsencrypt” makes things easy now: After you’ve run it successfully, it will create a new certificate on a monthly base. This certificate is valid for 3 month.


    • Port forwarding set up
    • A valid DNS-entry
  • custom_nodename set



Script is using the email adress of first user in SOUL

During script execution connection to SOUL is interrupted.

Run script from console or local network.


  • If you are navigating to a Protonet server listening to a custom domain via http (port 80) you are automatically being forwarded to https (port 443)
  • On iOS a new Apple touch icon has been applied, if you add SOUL to the home screen via browser
  • Forgot your password? – You won’t see anymore, if an email address is in use by anyone
  • Calendar weeks are shown in German calendar view



  • In calendar week view it is no longer necessary to click twice to move to the next week.
  • You do not need to reload SOUL any longer, if you have added someone to a private chat and want to mention him
  • Using Windows tablets you can create events again via touch pad
  • Samba user rights got further restricted as a result of a penetration test
  • Webserver configuration got further restricted as a result of a penetration test


Thanks to our partner Systemgemisch UG and binsec GmbH for penetration testing.

*Let’s Encrypt is a so called certificate authority. This is providing trustworthy certificates: The usage of these certificates is only posisble, if you can prove accessibility of the website you requested the certificate for. Let’s Encrypt is testing this by starting a specific webserver on the target system, on which a test file must be reachable.