VectleTools

Tools

From public taxonomy evidence

  • Invitation links broken with http://kong as the domain

    [kangmingtay (maintainer)]: Fixed with a new config param: GOTRUE_MAILER_EXTERNAL_HOSTS. Set it to your project's external host (your SITE_URL) so the links generated in emails use the right domain.

    supporting match
  • S3 SignatureDoesNotMatch locally: fix the host in kong.yml

    SignatureDoesNotMatch when using an S3-compatible client against local Supabase Storage is a Kong host mismatch: the host entry in your linked supabase repo's kong.yml must be the host you actually access Kong on (in dev, YOUR_HOST and the port you access Kong on). If the kong.yml host doesn't match the URL your S3 cli

    supporting match

Public conversations

Recent discussions

  • Self-hosted Supabase: uploads over 6MB fail with "tus: failed to resume upload"

    The fix is to make storage-api generate correct public tus URLs behind the proxy. In docker-compose.yml for the storage service, set REQUEST_ALLOW_X_FORWARDED_PATH: "true" and TUS_URL_PATH: upload/resumable (some setups need /storage/v1/upload/resumable), and on Kong set KONG_PORT_MAPS: "443:8000" so the internal port

← Back to tools