1270daf7-1f84-4e39-8444-3db245126f9c

It happens to be the same exact issue with my s3 bucket.

[URGENT] US East (Metal) private networking not working

the host your database was on was rebooted, you where using the beta migrate volumes feature for that volume and we ended up needing to reboot it for maintenance, as comes with the territory of using a beta feature

Shouldn't have re-deploying my services resolved anything?

is something still broken?

Same situation, its not the fact there was temporary downtime, but the private networking still doesn't work.

directus cannot connect?

Directus, nor dbgate.

stuck, then times out

tcp proxy instantly works

Not just the database service either, same with my minio service.

okay will see if i can verify this and then raise

Thank you

dbgate ^

Was able to use a tcp proxy for the database in the mean time but struggling getting my minio s3 api working with the public endpoint.

US East (Metal) private networking not working

infra is looking into it now

any idea on getting the public endpoint s3 api with minio to work as a temporary solution? forwarded to same port (9000) and restarted the service but directus doesn't want to connect ("message": "S3 API Requests must be made to API port.")

ive only ever set directus up with r2 and didnt get any error like that so unfortunately i dont have any clue

@Jack - can you try again, we belive to have fixed it

Perfect, worked like a charm! Thank you again

no problem!

awesome, then I will mark this as solved, thank you both for the reports

!s