Laravel 10 Support

[rulyce23]

does laravel 10 is compatible with this hosting? because i was uploaded the file with ftp filezilla and also was configuring the .env but the result like in image i was shared…please help, because i near hit the deathline time

[KangJL]

Please read

Http error 500

When trying to access your website, you may see a page which returns the status code “500”. In Google Chrome, you’ll see a page with the error code HTTP ERROR 500. There are typically two reasons which can cause this error: The PHP code has crashed. The .htaccess file contains invalid rules. Here are some things you can try to debug and fix this. Fixing crashing PHP code A HTTP ERROR 500 simply tells you that the PHP code has crashed, but gives no information as to why it has crashed. Gett…

[rulyce23]

i was read it many time…but only at this time,idk why?

[Dev-I-J]

Have you uploaded all the files? looks like package sebastian/version is missing or not uploaded correctly. Make sure you upload all files and folders including the vendor folder.

[rulyce23]

idk what is that means…can you help reaching this out?

[Dev-I-J]

proc_open is blocked on free hosting. Also according to my understanding vendor folder should be in /htdocs along with app, config, etc. Why did you upload it into /htdocs/laravel?

[rulyce23]

ouuh vendor must be in htdocs only? not inside folder of laravel? ok i will try this, because i forgot about use the laravel 10 and so i just watch youtube about how to upload via filezilla sir

[Dev-I-J]

Not only vendor, but all laravel folders like app, config, public etc should be in /htdocs. Make sure your directory structure looks like this. (ie. everything should be in /htdocs not /htdocs/laravel)

[Admin]

@Dev-I-J

Also according to my understanding vendor folder should be in /htdocs along with app, config, etc. Why did you upload it into /htdocs/laravel?

No, this is fine. There are roughly two ways to setup Laravel here: you can keep the folder structure in-tact and use .htaccess rules, or you can move the entire Laravel installation in a subfolder, move the contents of the public folder to the root folder, and update the index.php to reference the new path.

I tend to recommend the .htaccess method, because it’s simpler and doesn’t involve restructuring your codebase, but both methods should work equally well.

@rulyce23

idk what is that means…can you help reaching this out?

Looking at the stack trace, I’m guessing that some PHP code is trying to execute a command to determine the code version used. Specifically, it’s underlying code of the nunomaduro/collision package.

However, at least in vanilla Laravel, this package is only part of the development dependencies, which shouldn’t be included in a live site to begin with. You can generate a vendor folder without the development dependencies with this command:

composer install --no-dev

Then replace the currently uploaded vendor folder with the new one you just generated. That should fix this issue.