1 Go to https jwt io 2 In the payload field add the followin Supabase #off-topic

1: Go to https://jwt.io/ 2: In the 'payload' fie...

Scott P

08/29/2021, 11:51 PM

1: Go to https://jwt.io/ 2: In the 'payload' field, add the following (source: https://supabase.io/docs/guides/self-hosting#configuring-each-service):

Copy code

json
{
 "iss": "supabase",
 "iat": 1603968834,
 "exp": 2550653634,
 "aud": "",
 "sub": "",
 "role": "service_role"
}

3: In the 'verify signature' field, add your service-role JWT found in the dashboard. 4: The generated JWT is your API key Alternatively, use the anon JSON from the link above, and add your public JWT key instead in the instructions above. It might even be possible to just use the API key that's listed in the dashboard instead of going through this process. It might work, it might not - I can't remember the full technicalities of it. Let's move this to a thread so it doesn't clutter up general any more

tinjaw

08/30/2021, 12:05 AM

My worker is throwing an different error now

tinjaw

08/30/2021, 12:06 AM

Copy code

{
  "exceptionDetails": {
    "columnNumber": 6647,
    "exception": {
      "className": "TypeError",
      "description": "TypeError: Invalid URL string.\n    at new c (worker.js:1:6649)\n    at d.from (worker.js:1:8717)\n    at worker.js:1:9089\n    at worker.js:1:9215",
      "preview": null,
      "subtype": "error",
      "type": "object",
      "value": null
    },
    "lineNumber": 0,
    "text": "Uncaught (in promise)",
    "url": "worker.js"
  },
  "timestamp": 1630281861804
}

tinjaw

08/30/2021, 12:17 AM

I freely admit that I am burnt out

tinjaw

08/30/2021, 12:17 AM

But I have no choice but to keep working on this

tinjaw

08/30/2021, 12:59 AM

Now cloudflare is giving me problems posting my code

tinjaw

08/30/2021, 1:06 AM

Well, now I can't even test my code any more because of https://github.com/cloudflare/wrangler/issues/1129

tinjaw

08/30/2021, 1:06 AM

Time to abandon this for today.

kelvin.pompey

08/30/2021, 5:09 PM

@User Something interesting is if I use postgrest-js with the postgrest endpoint on port 3000 with the same anon token it works.

kelvin.pompey

08/30/2021, 8:37 PM

@User I believe I've resolved the issue. The contents of /var/lib/kong/kong.yml was not up-to-date with the changes that I had made to kong.yml in dockerfiles, so I manually replaced it, ran kong reload and now it works! Thank you for the assistance.

Previous Next