Sebastian Scheibner

Indeed restoring from Android backups is not supported yet, and might never be supported. signal-cli also doesn't store a message history so restoring the backup is not that useful.

See https://github.com/AsamK/signal-cli/blob/master/lib/src/main/java/org/asamk/signal/manager/config/LiveConfig.java#L35

Looks like there's an option in libsignal-clietn to resolve hostnames locally or remotely by the proxy. But it's hard coded to resolve locally... https://github.com/signalapp/libsignal/blob/main/rust/net/infra/src/route/proxy.rs#L216

This appears to have been changed in libsignal 0.81.0: https://github.com/signalapp/libsignal/commit/15d18cab82be1013ba610e9a2084bd05d268681b So with the next signal-cli release the dns lookup should be deferred to the proxy.

There'll be a new release in the next few days. Can you test if your proxy configuration now works with the latest development build? https://github.com/AsamK/signal-cli/actions/runs/17839744334

hm, the rate-limit response already includes the "id" field, which corresponds to the id of the send message request. So using that you should already have the information which account...

You might have too many linked devices already. You can check with the `listDevices` command and remove old devices with `removeDevice`

Thanks for confirming, I'll leave this open to add a better error message for DeviceLimitExceededException

Hard to say what's going on, when sending a new session should be created automatically ... Maybe some inconsistency with aci/pni stores.

Thanks, I think I found the issue. In Signal-Android new sessions are cached in `BufferedSessionStore`, so signal-cli has to do the same.