Does the VPS have some sort of control panel like Plesk or cPanel. You could try using that to remove the files. Then take the zip file for kirby from the get kirby site and upload that zip file through the file manager provided with cPanel or Plesk. Then use the file manager to unpack the zip file. This should work, and all the files should be written with all the correct permissions since the file manager did it.
@Brindavoine The first thing we need to know is if subpages work. If they do, we probably donāt have a problem with the .htaccess
-
@texnixe http://plmcch.fr/photography is reachable. The images donāt load
@jimbobrjames VestaCp is installed on the vps, but the kirby installation failed with the softaculous component.
Ok, thatās because the images cannot be moved to the media folder.
Ok, Vesta should be able to to it, but try manually as i described, rather than an automated system.
Iāve tried to correct the config.php file (2 returns instructions as you pointed @texnixe), with :
-filezilla,
-ssh
-vestacp file manager.
Same errors : iām unable to save the modification. There must be an error in my permission. Donāt know.
Iāll try it.
Edit :
It works !
Iāve done a wget to the master.zip file, then unzip, then I moved the file to the root of my site.
Iām still confused with the permissions
Should I change them ?
If its working, I would leave them alone
Just delete the master.zip
file. I suspect admin
user has the correct rights, or belongs to the correct group. You could try running a command to see all the users and groups on the VPS and figure out that way which one is the best one to use going forward. Plenty of help on google for this. However OVH should have told you the correct user:group to use.
Sorry I didnāt check my notifications :s . Ovh was not able to help me so it stayed broken. Iām glad you found a solution tho and will definitely try to follow these steps. So thanks to you guys !
I had this same issue today and realized I had forgotten to include the trailing semicolon after the closing bracket in my site/config/configā¦ environment setting (after updating to Kirby 3). That one semicolon wouldnāt send any errors to the php log but prevented the site from loading. Just posting here in case anyone comes along with a similar blank screen. Thanks for the idea @texnixe!