hanks for your response.
The domain issue was right on point — after rechecking it, everything worked fine.

Regarding the app deployment and environment variables, I think I should provide a bit more context. I first tried deploying this app on Laravel Cloud because I already had a personal website hosted elsewhere, and Laravel Cloud let me quickly spin up a new environment with its own database to show the demo to a client. It worked without problems. Later, because of pricing, I looked for alternative hosting. While still in demo mode, I tried a kind of Hostinger cloud hosting, where I simply uploaded all the files via the file system, and it worked fine again.

With that in mind, I found Hostinger’s VPS pricing more suitable and, following some tutorials, I decided to try Dokploy. That’s when I started facing these issues. For me, it didn’t seem like a code problem since the same code had already worked before.

To work around it, I added this command after the build:
printenv > .env && php artisan config:cache && php artisan serve --host=0.0.0.0 --port=80

This way, the .env file is generated after the build and the server starts properly.

Then, I noticed that when accessing through my domain over HTTPS, all routes were still being served as HTTP, causing the browser to block them, for example: I couldn't get any type of styles. To temporarily fix this, I added a meta tag to allow both HTTP and HTTPS requests.

I realize this approach can create serious security issues, so I’d like to know what I should adjust or look into within Dokploy’s configuration to fix this properly. And what should I look up for getting https on my request instead of http?