github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1118] Please set BETTER_AUTH_SECRET in your environment variables or pass secret in your auth config. #8603

New Issue
Closed
opened 2026-04-13 03:43:08 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-13 03:43:08 -05:00
Owner
Copy Link

Originally created by @jeffscottward on GitHub (Jan 4, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1118

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Setup very basic Astro.js and Better-Auth.
Run Astro.js preview command astro preview or similar depending on your choice of pnpm or npm etc

Current vs. Expected behavior

To not throw an error. I tried adding the secret to the config, and that didn't help either.

What version of Better Auth are you using?

latest as of Jan 3 2025

Provide environment information

Mac OS M1 Sonoma 14.6.1

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

Other

Auth config (if applicable)

export const auth = betterAuth({
  database: {
    dialect,
    type: "sqlite",
  },
  plugins: [
    magicLink({
      expiresIn: 5 * 60, // 5 minutes
      sendMagicLink: async ({ email, token, url }, request) => {
        await sendReactEmail({
          to: email,
          subject: "Sign in to site",
          text: `Click this link to sign in to site: ${url}`,
          template: MagicLinkEmail({
            magicLink: url,
          }),
        });
      },
    }),
  ],
});

Additional context

.env

BETTER_AUTH_URL=https://sampleurl.com
BETTER_AUTH_SECRET=QD2loiXIqtE8q1ES3Y5VVERFxlkqfLt7

terminal

astro preview

19:15:10 [@astrojs/node] Server listening on http://localhost:4321

[Better Auth] ERROR You are using the default secret. Please set BETTER_AUTH_SECRET in your environment variables or pass secret in your auth config.

Originally created by @jeffscottward on GitHub (Jan 4, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1118 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce Setup very basic Astro.js and Better-Auth. Run Astro.js preview command `astro preview` or similar depending on your choice of `pnpm` or `npm` etc ### Current vs. Expected behavior To not throw an error. I tried adding the secret to the config, and that didn't help either. ### What version of Better Auth are you using? latest as of Jan 3 2025 ### Provide environment information ```bash Mac OS M1 Sonoma 14.6.1 ``` ### Which area(s) are affected? (Select all that apply) Other ### Auth config (if applicable) ```typescript export const auth = betterAuth({ database: { dialect, type: "sqlite", }, plugins: [ magicLink({ expiresIn: 5 * 60, // 5 minutes sendMagicLink: async ({ email, token, url }, request) => { await sendReactEmail({ to: email, subject: "Sign in to site", text: `Click this link to sign in to site: ${url}`, template: MagicLinkEmail({ magicLink: url, }), }); }, }), ], }); ``` ### Additional context .env BETTER_AUTH_URL=https://sampleurl.com BETTER_AUTH_SECRET=QD2loiXIqtE8q1ES3Y5VVERFxlkqfLt7 terminal > astro preview 19:15:10 [@astrojs/node] Server listening on http://localhost:4321 [Better Auth] ERROR You are using the default secret. Please set BETTER_AUTH_SECRET in your environment variables or pass secret in your auth config.
GiteaMirror added the lockedbug labels 2026-04-13 03:43:08 -05:00
GiteaMirror commented 2026-04-13 03:43:10 -05:00
Author
Owner
Copy Link

@Scooter1337 commented on GitHub (Jan 4, 2025):

Make sure your .env file contents are loaded into process.env using e.g.

dotenv.config();

Or something similar.

<!-- gh-comment-id:2569977481 --> @Scooter1337 commented on GitHub (Jan 4, 2025): Make sure your `.env` file contents are loaded into `process.env` using e.g. ```typescript dotenv.config(); ``` Or something similar.
GiteaMirror commented 2026-04-13 03:43:11 -05:00
Author
Owner
Copy Link

@jeffscottward commented on GitHub (Jan 4, 2025):

It’s automatic. See the Astro.js docs
https://docs.astro.build/en/guides/environment-variables/

Jeff Scott Ward
Founder / A.I. & U.I. Engineer
F0.ai

On Fri, Jan 3, 2025 at 8:07 PM L.A. Verheul @.***>
wrote:

Make sure your .env file contents are loaded into process.env using e.g.

dotenv.config();

Or something similar.

—
Reply to this email directly, view it on GitHub
https://github.com/better-auth/better-auth/issues/1118#issuecomment-2569977481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUO7UJKVQXV5MMVRACPD32I4X4HAVCNFSM6AAAAABUSRBRPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRZHE3TONBYGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:2569996413 --> @jeffscottward commented on GitHub (Jan 4, 2025): It’s automatic. See the Astro.js docs https://docs.astro.build/en/guides/environment-variables/ ------------------------------ Jeff Scott Ward Founder / A.I. & U.I. Engineer *F0.ai* ------------------------------ On Fri, Jan 3, 2025 at 8:07 PM L.A. Verheul ***@***.***> wrote: > Make sure your .env file contents are loaded into process.env using e.g. > > dotenv.config(); > > Or something similar. > > — > Reply to this email directly, view it on GitHub > <https://github.com/better-auth/better-auth/issues/1118#issuecomment-2569977481>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAJUO7UJKVQXV5MMVRACPD32I4X4HAVCNFSM6AAAAABUSRBRPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRZHE3TONBYGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
GiteaMirror commented 2026-04-13 03:43:12 -05:00
Author
Owner
Copy Link

@Scooter1337 commented on GitHub (Jan 4, 2025):

It’s automatic. See the Astro.js docs https://docs.astro.build/en/guides/environment-variables/

Astro (Vite) loads them into import.meta.env, while better-auth uses process.env. That might be the inconsistency here?

<!-- gh-comment-id:2569998130 --> @Scooter1337 commented on GitHub (Jan 4, 2025): > It’s automatic. See the Astro.js docs https://docs.astro.build/en/guides/environment-variables/ Astro (Vite) loads them into import.meta.env, while better-auth uses process.env. That might be the inconsistency here?
GiteaMirror commented 2026-04-13 03:43:13 -05:00
Author
Owner
Copy Link

@jeffscottward commented on GitHub (Jan 4, 2025):

I tried the import meta method but it still didn’t take which really
surprised me and why I did file this bug.

Jeff Scott Ward
Founder / A.I. & U.I. Engineer
F0.ai

On Fri, Jan 3, 2025 at 8:54 PM L.A. Verheul @.***>
wrote:

It’s automatic. See the Astro.js docs
https://docs.astro.build/en/guides/environment-variables/

Astro (Vite) loads them into import.meta.env, while better-auth uses
process.env. That might be the inconsistency here?

—
Reply to this email directly, view it on GitHub
https://github.com/better-auth/better-auth/issues/1118#issuecomment-2569998130,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUO7QY4SDC7JNUNWNJIKT2I45MNAVCNFSM6AAAAABUSRBRPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRZHE4TQMJTGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:2570022242 --> @jeffscottward commented on GitHub (Jan 4, 2025): I tried the import meta method but it still didn’t take which really surprised me and why I did file this bug. ------------------------------ Jeff Scott Ward Founder / A.I. & U.I. Engineer *F0.ai* ------------------------------ On Fri, Jan 3, 2025 at 8:54 PM L.A. Verheul ***@***.***> wrote: > It’s automatic. See the Astro.js docs > https://docs.astro.build/en/guides/environment-variables/ > > Astro (Vite) loads them into import.meta.env, while better-auth uses > process.env. That might be the inconsistency here? > > — > Reply to this email directly, view it on GitHub > <https://github.com/better-auth/better-auth/issues/1118#issuecomment-2569998130>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAJUO7QY4SDC7JNUNWNJIKT2I45MNAVCNFSM6AAAAABUSRBRPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRZHE4TQMJTGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
GiteaMirror commented 2026-04-13 03:43:14 -05:00
Author
Owner
Copy Link

@ericclemmons commented on GitHub (Mar 21, 2025):

Similar setup, but I was able to confirm it works by passing secret:

export const auth = betterAuth({
  database: drizzleAdapter(db, { provider: "pg" }),
  emailAndPassword: {
    enabled: true,
  },
  secret: import.meta.env.BETTER_AUTH_SECRET,
});

I'd investigate there with console.info(...) and make sure it's being explicitly passed and all.

<!-- gh-comment-id:2743693329 --> @ericclemmons commented on GitHub (Mar 21, 2025): Similar setup, but I was able to confirm it works by passing `secret`: ```js export const auth = betterAuth({ database: drizzleAdapter(db, { provider: "pg" }), emailAndPassword: { enabled: true, }, secret: import.meta.env.BETTER_AUTH_SECRET, }); ``` I'd investigate there with `console.info(...)` and make sure it's being explicitly passed and all.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label bug locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8603
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?