digitalocean/supabase-on-do

Magic Link SSL Certificate

Closed this issue · 13 comments

Is there something in the domain config I am supposed to do? I have nameservers with Digital Ocean however with the magic link it generates the correct domain

but starts with

http://url2892.

When I go to the link I get the below error regarding SSL.

Screenshot 2023-03-04 at 15 52 32

is there something i need to config?

Is this the magic link to access your application (similar to what is created in the sample app)? If that's the case you need to set the site_url variable to your applications domain.

If you're running stuff locally, you might have to set the variable to localhost (it will give you an ssl error as the site url variable sets the address to https)

I haven't seen the url2892 thing before ever, is this something I have to change when I was setting up the docker stuff etc via the tutorial? @timothymamo

Not sure where url2892 is coming from. All you need to do is set the variables within the tfvars file.

As long as you are referencing your supabase instance with the your <YOUR_SUPABASE_URL> and <YOUR_SERVICE_ROLE_KEY> within your application it should work.

Within the application aren't we supposed to use the ANON_KEY instead of the SERVICE_ROLE key??

You're right sorry, should be ANON_KEY.

That's all fine I honestly have no idea about this type of stuff! All that is set fine in the tfvars file I have

region    = "ams3"
domain    = "createyourzen.app"
timezone  = "Europe/London"
auth_user = "*****"
site_url  = "supabase.createyourzen.app"

is site_url supposed to be the subdomain you access supabase from right? (as that is currently working fine)

Ahhh that's where I went wrong, the site_url also had to match and be the applications URL. Not what I intended for the supabase application to work on

https://github.com/digitalocean/supabase-on-do/blob/main/terraform/README.md#:~:text=site_url,in%20the%20format.

Ahhhh ok, the site_url should be createyourzen.app (no need to add https:// as that is added automatically)

@timothymamo sorry for being an absolute silly person and not fully reading into the docs... Once I update the vars am i able to apply and run again for it to be updated to be updated on current droplet? Or do I have to spool up a new droplet

For everything to apply when changing environment variables you'll need to either spin up another droplet or restart the containers within the droplet.

I'll spin up a new droplet! Thank you so much @timothymamo i'll see how this gets on and works

Thank you for your time on a saturday!!!

Hopefully it all works out, enjoy your Saturday. Feel free to reach out whenever, but I'll log off for the weekend 😃