Seems weird that you’re not seeing any logs for service2 in caddy, especially if it’s caddy serving the 502. I’d expect at least a message from caddy complaining about being unable to reach the upstream service in that case.
Verify that the 502 is coming from caddy and not potentially some other gateway that’s part of service2.
Personally I’ve just had issues with pocket mode not registering and combining that with liking tap-to-wake, lift-to-wake I ended up calling my emergency contact way too many times. Still not fixed.
Also, I thought it was standard to allow for forward/backward by long pressing the volume buttons, but that option isn’t available apparently either.
It’s battery optimization is also a bit shite to be honest, however I don’t know of any manufacturer that doesn’t run afoul when it comes to that aspect.
Minor gripes really, but it feels like it could be more polished and while the UI isn’t modified too atrociously, given the above issues I’m wary of what else they’ve modified under the hood.
Yea, no, that log entry doesn’t really shed any light on the issue.
However, your comment regarding having configured ActualBudget to serve the certificate might be hinting at what’s wrong.
Since your chain is
client > caddy > actualyou should be following the guide by actualbudget regarding operating behind a reverse proxy, so actual should not be serving the certificate.You’ll likely want/need to configure actualBudget to trust your proxy as well https://actualbudget.org/docs/config/#trustedproxies