@IngoPan, since you're running pixelserv, I'm happy to offer you a few words about your setup posted in #56.
Your
service-start looks okay. The line to start pixelserv-tls is redundant although it doesn't hurt either. As you install pixelserv-tls from Entware-ng, it'll be automatically started as part of
rc.unslung that follows. To keep it simple, you can simply remove the pixelserv-tls line.
Looking at your servstats, it shows you haven't created
ca.crt and
ca.key, follow
the simple steps here to get them created. I would at the minimum get this CA cert created.
Optionally you would want to import
ca.crt into your client devices. Follow the steps
here. Don't feel obliged to import ca.crt. Without it your client devices just work (contrary to the opposite belief) with no ill effect. Personally I don't bother import ca.crt into my TV, internet radio etc. I only import on my major browsing devices such as phones, tablets and PC.
Since I'm looking at your
services-start, I would simply unload my rant. I have huge issue with ill advice scattered on this forum that I saw before. It's bad idea to add a few seconds of sleep here and there as well as polling loops in various "custom scripts". A better place to start Entware-ng will be to call rc.unslung inside
post-mount (not services-start). You can read my example posted here:
http://www.snbforums.com/threads/syncthing-ac68u.27030/#post-207695. There you won't need the "until" polling loop for pen drive to be available. The 1 second sleep will go too. Anyway, just my attempt to help you having a robust system. You don't have to change if your main focus is simply functionality.