Again not natively unfortunately, but Guild Wars 2 runs pretty well, even on the steam deck!

The base game is free to play, so no problem in testing it.

Typing this from a ZenFone 9.

I like the physical parts of it, camera's good, but OS leaves a bit to desire. The largest gripe which I experience daily is it's horrendous pocket detection, or rather lack thereof. Until I figured out what tap-to-wake and other combos to disable, it went off in my pocket and pocket dialed my emergency contact at least five times daily. Now I've only had issues once a month or so.

I put up with it, since there's no other brand making a similarly sized phone, with good camera and 3.5mm jack.

Highlight suggestion with arrow keys, shift + del, success?

Thanks for the tip, unfortunately I really dislike the idea of the screen being the externally facing portion of the phone.

Seems to me like presenting the most fragile part of the phone to the outside is less than ideal.

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 > actual you 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

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.

Sweet, just keep in mind that the connection between caddy and actual is just a plain HTTP one. Since your connection is in your local network that's fine, but if you were to change that then be mindful that you are placing an implicit trust on the networking between caddy and actual.

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.