Question Issue with Laravel on Plesk server - Domain not pointing to the correct directory

[JensS]

Description: Hello everyone,​

I’m running a Laravel application on my server, which is managed via Plesk. The domain is registered through Strato and has been correctly pointed to my server. However, the site is not loading as expected. Instead of the Laravel application, I’m seeing either the default Laravel page or the Plesk site preview.

Here are a few details:

• The domain is correctly pointing to the server (via Strato A-Record).
• In the Plesk-Site-Preview, the following URL is displayed: http://85.xx.x.xx./plesk-site-preview/www.huresco.org/https/85.xx.xx.xxx/
• It seems that the /public folder of the Laravel app is not being correctly accessed.

Error logs show:

bash
Code kopieren
404 GET /manifest.json HTTP/1.0
404 GET /runtime-service-worker.js

Here’s what I’ve checked so far:

1. Document Root is set to /public.
2. .htaccess in the public directory contains the standard Laravel rules.
3. Cache has been cleared in Laravel (php artisan config:clear, route:clear, etc.).
4. DNS entries at Strato are correct (A-Record for the main domain, CNAME for www).
5. SSL is enabled and working.

Does anyone have any ideas what I might be missing or how I can correctly point the domain to the Laravel app in the /public directory?

Thanks in advance for your help!

 

[jcapln]

Hallo !

did you create a Laravel skeleton with the laravel Toolkit or install all your Laravel app from Git ?
Rgds,

 

[JensS]

Hello!

I installed Laravel with Plesk and then the SiteJet Builder as a tool. Kind regards

 

[mauricekindermann]

Yeah this has been a probem for at least a year.
1. Create a new webspace
2. Choose Laravel
3. Now, before installing form GIT, you have to configure PHP + Document Root
- By default this is httpdocs.
- You cannot remove httpdocs as it requires an input
- So I change it to public
- But now laravel installs into /root/public/app/public

I cannot find a way around this yet. But I need one and am trying all methods I can think of.

 

[mauricekindermann]

Ok yes this is currently impossible to do in a new webspace. I have tried

1. Creating via existing Github Repo (cannot install into document root, only public/public)
2. Creating via skeleton (does not allow me to clone the project and laravel toolkit to function properly after)
3. Create blank site, install via git, then scan for laravel app. Same issue as point 2, laravel toolkit does not function properly

 

[mauricekindermann]

Sadly, until this is fixed, we will have to live with a document root of /public/public

 

[mauricekindermann]

Spent several hours here debugging every which way possible.

In the end it is not possible to install laravel on a new webspace.

I tried to install it into /laravel/public. And even though it 'works' on the backend, even static files in /laravel/public/test.svg do not resolve.

I am assuming there is some weird systemlink issue happening.

If I do get it I will report back. But leaving my notes here in case anyone has an idea.

 

[Raul A.]

What do you have in Hostings for the website in Plesk?

 

[mauricekindermann]

Finally got it. Final issue for me was plesk apache/nginx auto-blocking system links.

So it is possible to use home/laravel/public

But it's not possible to do what I've done in the past, which was home/public