CP doens't work after deploy

[AnnelynnTruyens]

I just deployed my statamic site using Digital Ocean App Platform.

My frontend site works, but I can't access my control panel anymore. I get a 500 server error when trying to access it.
I got this error before with my frontend as well, because my env variables were not yet added. So I assume it's a problem with my env variables, does anyone know which one could be the problem for the control panel?

[duncanmcclean]

Are you able to access the Laravel log? It'll usually tell you what error is occurring, then you can fix it from there.

Normally, you'd find your Laravel log file in storage/logs but I'm not sure where/if it's accessible within DigitalOcean App Platform.

[duncanmcclean]

Unfortunately, that's the wrong sort of log. It just says which URLs were hit and by what (eg. browser). It's not the Laravel log file, which is needed to figure out the error.

[AnnelynnTruyens]

Then I have no idea where or if I can find them on DigitalOcean. I can only see the local log files in my local folder, but not the ones of the deployed website.

[duncanmcclean]

I've never used DigitalOcean App Platform before but from the outside it doesn't look like it's possible to see "application" logs. 🤔

Another option would be to temporarily enable debug mode but I would make sure you disable it as soon as possible since it's a big security risk.

Alternatively, you could try using something like Forge or Ploi with a DigitalOcean droplet. They give you much more control over your server.

[AnnelynnTruyens]

I temporarily enabled debug mode and found the problem. My cp.css and cp.js were not found with the build as I'm not using those files, but they were put in the boot function in the AppServiceProvider.php. I deleted that part of the code in that file and the problem is now solved. Thank you for your help!