norrisduncan

I am also having this problem running the Medusa admin on a remote machine. The admin dashboard will use my remote machine's address when I run it in production mode...

I bet this clue has something to do with it. I believe this would be in node_modules/@medusajs/admin-ui/vite.config.dev.ts in your project structure, but I found it on GitHub at https://github.com/medusajs/medusa/blob/master/packages/admin-ui/vite.config.dev.ts 

> This is not just a Google Cloud issue then. How are we the only people running into this issue? I suspect it's because 1. it only happens when serving...

I think I was able to figure it out... Something is overwriting process.env.MEDUSA_BACKEND_URL with "http://localhost:9000", no matter what I do. I should have written down my steps, but I think...

Here you go: .env relevant lines ``` STORE_CORS=http://[[myDomainName]]:8000,http://[[myDomainName]]:7001 ADMIN_CORS=http://[[myDomainName]]:7000,http://[[myDomainName]]:7001 MEDUSA_BACKEND_URL=http://[[myDomainName]] COOKIE_SECRET=supersecret JWT_SECRET=supersecret ``` My whole medusa-config.js: ``` const dotenv = require("dotenv"); let ENV_FILE_NAME = ""; switch (process.env.NODE_ENV) { case "production":...