Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Supabase: An error occurred while setting up the SSL connection #3050

Closed
1 of 2 tasks
tschuehly opened this issue Aug 11, 2024 · 4 comments · Fixed by #4598
Closed
1 of 2 tasks

[Bug]: Supabase: An error occurred while setting up the SSL connection #3050

tschuehly opened this issue Aug 11, 2024 · 4 comments · Fixed by #4598

Comments

@tschuehly
Copy link

Description

Hello!

I've set up Supabase on a fresh coolify install and can successfully connect to the supabase dashboard. But I cannot connect to the Postgres DB. I've tried both with port 8000 and 5432. The error happens both with JDBC and in IntelliJ.

image

Minimal Reproduction (if possible, example repository)

Set up coolify, and supabase. Add a domain record and change it to the domain. Try to connect with a JDBC client.

Exception or Error

No response

Version

v4.0.0-beta.323

Cloud?

  • Yes
  • No
@djsisson
Copy link
Contributor

have you amended the compose file to expose the ports from the container to the host?

@tschuehly
Copy link
Author

have you amended the compose file to expose the ports from the container to the host?

Nope, isn't that happening via Kong? Then that's an easy fix, will try it out.

@djsisson
Copy link
Contributor

you could also just use an ssh tunnel

@roshi112
Copy link

have you amended the compose file to expose the ports from the container to the host?

Nope, isn't that happening via Kong? Then that's an easy fix, will try it out.

hello can you please explain, i am facing same problem, the .well-known directory is not public thus giving 401 error when issuing the ssl.

kind regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants