Cannot create admin user

nballlast year

20

import dotenv from 'dotenv'
import path from 'path'
import { buildConfig } from 'payload/config'

import { Pages } from './collections/Pages'
import { Users } from './collections/Users'

dotenv.config()

export default buildConfig({
  admin: { user: Users.slug }, // added this in testing, no effect
  collections: [Pages, Users],
  cors: [process.env.PAYLOAD_PUBLIC_SERVER_URL, process.env.PAYLOAD_PUBLIC_SITE_URL],
  csrf: [process.env.PAYLOAD_PUBLIC_SERVER_URL, process.env.PAYLOAD_PUBLIC_SITE_URL],
  typescript: {
    outputFile: path.resolve(__dirname, 'payload-types.ts'),
  },
})

• 

  jacobsfletch

  last year

  @511305637959827459

  it sounds like your cookie settings are incorrect, likely due to your env not loading properly. Double check your import statement for

  dotenv

  . I think the proper way to import this module using ES6 syntax is

  import {} from 'dotenv/config';

  although I typically opt for CommonJS like this

  require('dotenv').config()
• 

  nballlast year

  Aha, will do!

  
  
  @808734492645785600

  I tried this, builds and deploys, but get an error when visiting /admin. I was attempting to use this approach

  https://discord.com/channels/967097582721572934/1098088422553440256

  which had worked for me earlier.

  
  
  Uncaught TypeError: n(...).config is not a function

  in browser console after successful deployment.

• 

  jacobsfletch

  last year

  Hmmmm strange error

  
  
  

  But I do think another problem is that your importing the env

  after

  your collections

• 

  nballlast year

  Haha yeah, today is my auth/access/cors/csrf deep dive.

  
  
  

  OH!

  
  
  

  I hadn't considered that … at all

• 

  jacobsfletch

  last year

  So it a fun day for you sounds like haha

  
  
  

  Yea your cookie domain in your users collections probably is setting an undefined property

• 

  nballlast year

  Thank you, and the whole team, for being here for us n00bs while we learn!

• 

  jacobsfletch

  last year

  We're all learning, it's a win-win 👍

  
  
  

  Let me know if you still have any troubles here

• 

  nballlast year

  Weird, same issue. Checking ENV on cloud but I am 99% certain they're correct.

  
  
  
  
  

  ENV are correct. COOKIE_DOMAIN is set to localhost, that shouldn't affect my ability to access the cloud admin, or should it?
• 

  jacobsfletch

  last year

  oh yea

  COOKIE_DOMAIN

  needs to be the live domain, just like

  cors

  and

  csrf
  
  

  because otherwise your cookie will not attach to your browser

• 

  nballlast year

  How does one test preview etc locally with cloud?

  
  
  

  localhost:3000 <--> payloadcms.app kinda thing

  
  
  

  Where local would be next.js with the intent to deploy to vercel, for example

• 

  jacobsfletch

  last year

  You could run the CMS locally alongside your Next.js app

  
  
  

  While connecting to the same Mongo instance, if needed

• 

  nballlast year

  Ah yes, I was doing that earlier and it worked well. Huh. Definitely learning here. Ok, thank you. I have somewhat of an idea how to make the preview example work now.

  
  
  

  Should cookie domain be the cms or the front end?

  
  
  

  Not seeing documentation on that, unless it's in the JWT library?

  
  
  https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#third-party_cookies
  
  

  And here I thought I had a handle on cookies this whole time, sigh

  
  
  

  The preview example is what is getting me turned around, because the cookie domain is the same for the front and back ends 😄

• 

  jacobsfletch

  last year

  The cookie domain is the domain of any site you wish to allow cookies for

• 

  nballlast year

  Can that be an array like cors or csrf?

• 

  jacobsfletch

  last year

  This excludes the protocol, i.e.

  payloadcms.com

  would work for a

  local.payloadcms.com

  front-end and a

  cms.local.payloadcms.com

  backend

  
  
  

  It cannot be an array, without looking the MDN docs there should indicate that

• 

  nballlast year

  BE and FE will have different domains

• 

  jacobsfletch

  last year

  Then you won't be able to take advantage of the security that the cookie domain provides

  
  
  

  Just use

  auth: true
• 

  nballlast year

  Aha, ok.

  
  
  

  Thank you again!

• 

  jacobsfletch

  last year

  No problem!

• 

  nballlast year

  @808734492645785600

  I was incorrect, my plan is to use a single domain. For example, CMS =

  https://edit.gravybo.at

  (currently set up as a CNAME in the Vercel DNS), dig shows it's functioning, however I am getting an SSL error

  SSL_ERROR_NO_CYPHER_OVERLAP

  where the parent domain SSL is fine, as is the destination value:

  https://gb.payloadcms.app
  
  

  I feel like there should be a separate thread.