I think I found the problem, since safe-mode still shows only a blank page I checked my Nginx logs more carefully and found this:
2017/06/03 14:38:39 [crit] 21647#21647: *45150 open() "/var/cache/nginx/proxy_temp/5/44/0000002445" failed (13: Permission denied) while reading upstream, client: 84.152.193.65, server: www.kokoro-ko.de, request: "GET /assets/vendor-199fce5a9e9895329b51b04605f1f5061951acb488baa6b2ea2fc2ae36def529.js HTTP/2.0", upstream: "http://unix:/var/discourse/shared/standalone/nginx.http.sock:/assets/vendor-199fce5a9e9895329b51b04605f1f5061951acb488baa6b2ea2fc2ae36def529.js", host: "www.kokoro-ko.de", referrer: "https://www.kokoro-ko.de/"
So I checked the folder permissions for /var/cache/nginx/proxy_temp/:
drwx------ 90 www-data www-data 4096 Jun 3 14:26 0
drwx------ 3 nginx nginx 4096 Jan 8 01:44 1
drwx------ 3 nginx nginx 4096 Jan 8 01:44 2
drwx------ 3 nginx nginx 4096 Jan 8 01:44 3
drwx------ 3 nginx nginx 4096 Jan 8 01:44 4
drwx------ 3 nginx nginx 4096 Jan 8 01:44 5
drwx------ 92 www-data www-data 4096 Mai 27 23:12 6
drwx------ 92 www-data www-data 4096 Mai 25 11:04 7
drwx------ 88 www-data www-data 4096 Jun 3 14:26 8
drwx------ 88 www-data www-data 4096 Jun 3 14:26 9
While my Nginx worker uses the www-data account
I adjusted the folder permissions and now it seems to work like it should
I need further testing for this but I didn’t know about safe-mode before which leaded me to the real issue!