I thought that might be enough but it seems putting "https" into SS_BASE_URL is not having the intended effect

Best as I can tell, the server is SSL but the SS installation behind it is not, which causes the base url to serve HTTP. The result is insecure content warnings

alternate_protocol seems to be removed in SS 4.2... what's the recommended approach for serving SS4 with php-fpm and nginx?

but your background mind is always working and analysing during sleep.

I kinda hate it, because it makes me sleep less and not near as sound

I love hamock driven design... waking up with a solution to a problem feels so fine