-
Notifications
You must be signed in to change notification settings - Fork 493
Closed
Closed
Copy link
Labels
bugSomething isn't workingSomething isn't workingsupabase-jsRelated to the supabase-js library.Related to the supabase-js library.
Description
Describe the bug

Getting timeout. not able to subscribed when running in container deploy on AWS ECS
What have i checked
- ✅ Public Security Group
- ✅ Public Subnet
- ✅ Route Table to Interget Gateway
- ✅ DNS hostname resolution
- ✅ IPv4 Generated
i tried all connection using curl
in container
and it get response immediately,
However, only the node to supabase-js client (as in screenshot)
show time out (TIMED_OUT
)
System information
- Container, NodeJS:20 bookworm
- Version of supabase-js: 2.57.0
- Version of Node.js: 20
Library affected
supabase-js
Reproduction
No response
Steps to reproduce
No response
System Info
node js v20
Used Package Manager
npm
Logs
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Supabase JS Library issue and not an issue with the Supabase platform. If it's a Supabase platform related bug, it should likely be reported to supabase/supabase instead.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingsupabase-jsRelated to the supabase-js library.Related to the supabase-js library.