Supabase template over HTTPS #26

Closed
opened 2025-11-22 20:29:25 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @maelp on GitHub (Apr 8, 2025).

To Reproduce

  • create the supabase template
  • serve it over an https endpoint
  • connect to supabase studio
  • go to the "auth" tab
  • try to create a user

it will complain that it tries to make a request over HTTP instead of HTTPS

Current vs. Expected behavior

It should work

Provide environment information

Latest

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Yes

Originally created by @maelp on GitHub (Apr 8, 2025). ### To Reproduce - create the supabase template - serve it over an https endpoint - connect to supabase studio - go to the "auth" tab - try to create a user it will complain that it tries to make a request over HTTP instead of HTTPS ### Current vs. Expected behavior It should work ### Provide environment information ```bash Latest ``` ### Which area(s) are affected? (Select all that apply) Application ### Are you deploying the applications where Dokploy is installed or on a remote server? Same server where Dokploy is installed ### Additional context _No response_ ### Will you send a PR to fix it? Yes
Author
Owner

@maelp commented on GitHub (Apr 8, 2025):

I updated all the "http://${SUPABASE_HOST}" to "https://${SUPABASE_HOST}" in the docker-compose and now it sends the payload, but it fails with an error that it cannot parse the JWT token or validate the signature

I do see the JWT token which seems to me like a valid JWT encoding (eg xxxx.yyyy.zzz where xxxx and yyy are b64 encoding of some JSON token)

@maelp commented on GitHub (Apr 8, 2025): I updated all the "http://${SUPABASE_HOST}" to "https://${SUPABASE_HOST}" in the docker-compose and now it sends the payload, but it fails with an error that it cannot parse the JWT token or validate the signature I do see the JWT token which seems to me like a valid JWT encoding (eg xxxx.yyyy.zzz where xxxx and yyy are b64 encoding of some JSON token)
Author
Owner

@Siumauricio commented on GitHub (Jun 1, 2025):

Recently a new template was implemented, and the old template was corrected, you can try it and check if you still have this problem.

So let's close this for now

@Siumauricio commented on GitHub (Jun 1, 2025): Recently a new template was implemented, and the old template was corrected, you can try it and check if you still have this problem. So let's close this for now
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#26