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).
Original GitHub issue: https://github.com/Dokploy/templates/issues/71
### 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
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)
<!-- gh-comment-id:2788315840 -->
@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)
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
<!-- gh-comment-id:2927920440 -->
@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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @maelp on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/71
To Reproduce
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
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
@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)
@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