Laravel Site Not Working

EthickS

After upgrading to v12 all the Laravel sites only getting 403 even restarting the Server, the php container and even the Server also rebooted but still not working...

Even the litespeed admin portal getting This site can’t be reached

xyzulu

Tried to reinstall php?
https://community.enhance.com/d/2415-enhance-v1200-released/178

Also, try switching to apache and then back again perhaps?

EthickS

I tried reinstalling php but didn't work try to switch to apache now total enhance server is down. I can't even connect to panel as well. What to do now xyzulu ?

Adam

Is the document root symlinked from somewhere else? If so, make sure the destination of that symlink has the group owner www-data.

EthickS

Adam No and checked the owner is www-data

Adam

Please send a support ticket, I will help you.

EthickS

Adam Hi Adam already raised and also mentioned some more issue that i have faced.

gmakhs

any solutions from support on this ?

Adam

In every case I have seen, it's the permissions on the document root which are the problem.

gmakhs

Adam Thank you Adam, i do have a lot of websites in Laravel and i am looking on a way of fixing it without going website by website

Adam

Is the path structure for every website the same? For example if your document root was app/public you could run:

chgrp -v www-data /var/www/*/app/public

gmakhs

Adam To be honest it might not be the same and the same issues occurs on 11 when someone is restoring a backup or migrating a website , it happens from time to time, i belive once the storm calms down you need to look in a better solution for that

EthickS

Adam Thanks it's working but WHMCS sites are not working what to do?

gmakhs

EthickS You need to find the location the Symlink goes and do the same, this is why i mentioned to @Adam that manually handling this is a TMP fix but not a solution

EthickS

gmakhs okay

Adam

The best solution is to set the document root directly to the public directory, then Enhance knows which directory to set the ownership on after a restore or migration. Enhance could potentially follow the symlink in future but it would need a lot of security around it.

gmakhs

Adam On the sites that i had the issue using Laravel the doc root is the public folder, the issue still occurs, i understand the reasons behind the fact that it can't follow the symlink, but on my case this means a lot of issues with laravel, whmcs and other scripts, so maybe we say that enhance is not production ready for anything that uses symlink outside of doc root?

Adam

gmakhs

A symlink outside of the doc root is ok (provided it is still inside the website's home dir), you just need to set the ownership (or permissions) manually.

If your doc root was set directly to the public folder then this should have happened as part of the update to v12.

If it's not working as expected please send a support ticket, I will help.