Simplify your stack and build anything. Or everything.
Build tomorrow’s web with a modern solution you truly own.
Code-based nature means you can build on top of it to power anything.
It’s time to take back your content infrastructure.

Payload starting, webpack compiled, but site cannot be reached after upgrading.

default discord avatar
markatomniuxlast year

Very strange issue that has started to occur around when version 1.14 was released. I upgraded my Payload instance from 1.11 to 1.14 and now when running Payload and navigating to /admin, the site cannot be reached. It's happened now on a couple of my projects, but replicating it seems difficult. The only commonality between the two projects is they were both updated to Payload 1.14. The frontend and the api are not responding. It is as if express cannot find the node app



I have tried rolling back Payload to version 1.11, deleting the database, refreshing my yarn cache, and deleting my node modules, but the problem persists.



The only warning I see in the console is

crbug/1173575, non-JS module files deprecated.

My current fix is creating a brand new Payload project. Obviously this isn't ideal so any help is appreciated!



A little bit of digging, payload.getAdminURL() is returning /admin, rather than

http://localhost:8000/admin

.



Error was entirely my fault. I had changed the name of my environment variable and as a result, the app was not using it properly.



However, I would have expected this message to have been flagged at some point -

https://github.com/payloadcms/payload/blob/6754f55ce0a09b1a765f19426ef269d09e1191c0/src/config/schema.ts#L27
    Star on GitHub

    Star

    Chat on Discord

    Discord

    online

    Can't find what you're looking for?

    Get dedicated engineering support directly from the Payload team.