Paul Stemmet

Hi @XBDRX So having investigated this a bit here's my analysis so far. ### Top level summary 1. Provide us with a TLS cert/key pair that is signed with the...

So, next steps are: - [x] (us) Modify our cert management - [x] (us) Create an endpoint in our dev environment using the ZeroSSL based cert - [x] (you) Test...

So I've created a MVP endpoint that should unblock your testing. Note that there is more work needed on our side to automate cert renewal, but you can find a...

So, I've not really looked at the client side at all, but looking at where the bridge is set, [here](https://github.com/WalletConnect/walletconnect-monorepo/blob/1.8.0/packages/clients/core/src/index.ts#L133), and the associated function, [getBridgeUrl](https://github.com/WalletConnect/walletconnect-monorepo/blob/1.8.0/packages/clients/core/src/url.ts#L36) it appears clients force an...

Great! If you're happy with that, then I'll get the work required to make this permanent into my queue, and keep you apprised on when we're ready to roll out...

As an update: I've just finished the feature work required for this in `dev`. I still need to do: - some testing - write up the documentation about the special...

After the above happens, you'll need to modify your `bridge` url to `https://fr0ntierx.bridge.walletconnect.org` --assuming you're happy with that prefix. I'll contact you when our end is ready

@XBDRX -- the production endpoint is now live! You can find it at `fr0ntierx.bridge.walletconnect.org`. I'll leave this issue open for the moment, in case something comes up. Also as a...

I've looked at this a couple times (as I'm affected by this myself), and believe it is a combination of two factors: 1. Go's default SIGHUP handling 2. Not setting...

At least in my environment there's two places this occurred: 1. At startup My nomad nodes are accompanied by Vault agents, and there's a `Before=nomad.service` clause so that the relevant...