Mixed up urls after renaming subdomain | Payload | Page 1

viscid granite Jul 2, 2023, 6:24 PM

#

Initially I had admin. subdomain. Now I changed it to cms.. Updated nginx rules, reissued certificates. Can load dashboard successfully from new subdomain.

However old subdomain is still appearing in some places - in initial message and in media urls (they are trying to load from admin.).
With media thumbnails are obviously not working, but also new ones not uploading and old ones not updating (not allowed to perform this action).

Inside main config file server url is loaded from .env file (updated value there to be new subdomain). And inside media collection config static url is also loaded from .env (just /media).

What can be wrong here?

viscid granite Jul 2, 2023, 7:01 PM

#

"Not allowed to perform this action" is acutally separate issue. It shows this error for any other collection or global

viscid granite Jul 2, 2023, 8:32 PM

#

Or perhaps not separate. If it is reading wrong domain, then it might as well be the reason
https://discord.com/channels/967097582721572934/1121089425833726002

viscid granite Jul 3, 2023, 2:06 AM

#

I checked multiple times. This variable contains new url. Yet when I build and start server, it says admin panel is available at old url. Does it cache env variables from build to build or something like that?

#

Well, it looks like that. Starting dev server uses new value, but building and starting prod server uses old value.

merry crypt Jul 3, 2023, 1:37 PM

#

@viscid granite Is it possible that your .env file is not getting updated on prod?

#

A lot of times deployments skip .env files

#

So it may be reading outdated urls in some cases

#

That's my first thought

viscid granite Jul 3, 2023, 1:52 PM

#

Is there special argument to force reading .env?

merry crypt Jul 3, 2023, 1:52 PM

#

Well, I would first check the .env file on your server and see what's in it

#

Are there any old references?

viscid granite Jul 3, 2023, 1:53 PM

#

No, I updated them

merry crypt Jul 3, 2023, 1:53 PM

#

Were there prior to me mentioning it?

viscid granite Jul 3, 2023, 1:54 PM

#

I updated them at the time of issuing new certificates for this subdomain, so yes

merry crypt Jul 3, 2023, 1:54 PM

#

ok so both your dev and prod .env files are consistent

viscid granite Jul 3, 2023, 1:54 PM

#

It is one file

merry crypt Jul 3, 2023, 1:55 PM

#

what im saying is

#

the .env file on your local machine has the same contents as the one on your prod machine?

viscid granite Jul 3, 2023, 1:56 PM

#

No

merry crypt Jul 3, 2023, 2:13 PM

#

hmm

#

Do you know why?

viscid granite Jul 3, 2023, 2:22 PM

#

Because localhost for local and domain name for prod

viscid granite Jul 4, 2023, 11:59 AM

#

Hardcoded value works as expected. So the problem is definitely in reading .env

#

Or can it be that old env variable was loaded into memory and never unloaded again, so config reads it from memory instead of file?

#

Or is it loading variable from different file? The one that is not .env in root folder?

viscid granite Jul 4, 2023, 9:12 PM

#

I found why it happens. It is pm2 preventing update of variables

merry crypt Jul 5, 2023, 12:19 PM

#

Ah yes

#

Happy you figured it out

viscid granite Jul 5, 2023, 3:50 PM

#

Only half way. The hard part is to make pm2 respect changes to .env file 😕

merry crypt Jul 5, 2023, 5:17 PM

#

@viscid granite pm2 takes a --update-env param

#

that should refresh your env file

viscid granite Jul 5, 2023, 5:19 PM

#

Tried that, not working

merry crypt Jul 5, 2023, 5:19 PM

#

how are you restarting pm2

#

when you push to prod

#

pm2 restart all

#

?

viscid granite Jul 5, 2023, 5:20 PM

#

No, startOrReload --only payload

merry crypt Jul 5, 2023, 5:20 PM

#

hmm

#

generally you would have an ecosystem.config.js

#

with your app config

viscid granite Jul 5, 2023, 5:21 PM

#

Yes, just named differently

merry crypt Jul 5, 2023, 5:21 PM

#

ah

#

then

#

pm2 restart MYAPP --update-env

viscid granite Jul 5, 2023, 5:21 PM

#

That bug was reported in 2014

merry crypt Jul 5, 2023, 5:21 PM

#

can you specify the name of the pm2 app explicitly?

viscid granite Jul 5, 2023, 5:21 PM

#

Names are defined in ecosystem file

merry crypt Jul 5, 2023, 5:22 PM

#

i mean, in the restart command

#

pm2 restart MYAPPNAME --update-env

viscid granite Jul 5, 2023, 5:22 PM

#

Yes, name or id, both work the same

merry crypt Jul 5, 2023, 5:22 PM

#

you've tried that

#

?\

viscid granite Jul 5, 2023, 5:23 PM

#

Restart command specifically - no

merry crypt Jul 5, 2023, 5:23 PM

#

I would first try that

#

my second thought is if you specify your env vars in your pm2 config rather than an env file

#

which seems odd, but is "recommended" by pm2

#

for instance

#

module.exports = {
  apps : [
      {
        name: "myapp",
        script: "./app.js",
        watch: true,
        env: {
          "NODE_ENV": "development",
        }
      }
  ]
}

#

never tried to do it that way

#

But first try the restart command

viscid granite Jul 5, 2023, 5:24 PM

#

Tried now, same result

merry crypt Jul 5, 2023, 5:25 PM

#

OK say you add those env vars to the env object in a pm2 config

#

Then when you run restart, you pass the changed env var and the flag

#

that should tell pm2 to replace the env var

#

kind of weird but worth a try

#

so you'd end up passing ENV_VAR=somethingnew pm2 restart app --update-env

#

and specify ENV_VAR in your env object in your pm2 config

#

that should update whatever your put as the default in the config file

#

@viscid granite Let me know if that works, sorry pm2 can be a bit weird

viscid granite Jul 5, 2023, 5:31 PM

#

That worked. And subsequent reset without variable works too now

merry crypt Jul 5, 2023, 5:32 PM

#

Woot! That's good to know

#

I'm glad we were able to figure it out

viscid granite Jul 5, 2023, 5:32 PM

#

🔥

merry crypt Jul 5, 2023, 5:32 PM

#

Let me know if anything else comes up

viscid granite Jul 5, 2023, 5:33 PM

#

The rest should work, just this one was new workflow for me

merry crypt Jul 5, 2023, 5:33 PM

#

PM2 is a nice, at first it was hard for me, but now I use it for all of my projects on deploy

#Mixed up urls after renaming subdomain