Hello,

After adding a TCP Proxy you must redeploy the database.

Well that's new... it did work after this. Because this was not needed before, I was sure that the service is just buggy/unstable and spent couple of hours retrying this. This frustration made me want to change providers, as it shows immaturity of the platform.

Could you elaborate on what appeared to be buggy/unstable?

When you add a TCP proxy we gotta re-init some network settings on our side, so a fresh redeploy is best. We should definitely prompt users to redeploy after they add one.

When I press "add" button, it fails 50% of the time. So this is before it even succeeds to add something and I need to restart.

Understood- we have some work on our end to refine the TCP proxy, there is an update we have in the works so we don't have to redeploy. However, without proper re-production, I can't get the TCP proxy creation to fail.

For now, I can mark this ticket as solved.

Wasted several hours on this issue, nowhere in the UI does it say or make obvious that a redeployment is required. Please reopen this thread/issue and atleast add a prompt or a hint or fire an automatic redeployment. Just a single alert/toast would suffice if nothing more. Should be relatively trivial to implement but might save someone several hours?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Thanks Zennoia, I setup some tracking to ensure we're monitoring this issue.

🛠️ The internal ticket TCP Proxy - Prompt User or Force Redeploy of database has been marked as todo.

🛠️ The internal ticket TCP Proxy - Prompt User or Force Redeploy of database has been marked as in progress.

Really happy to see the turnaround time! Thanks echohack!

✅ The internal ticket TCP Proxy - Prompt User or Force Redeploy of database has been marked as completed.