Check your error logs, what does it say specifically.
GoDaddy and Laravel
I install laravel on my godaddy hosting and I update laravel from version 5.0.2 to laravel 5.2.31 but I cant make to this work all the time I get error 500
I fix it its because I upgrade laravel then I delete whole installation and install with 5.2 version now everything work thanks so much :)
Hey, just curious: what kind of a plan are you using for GoDaddy? I had no idea they even offered these kinds of plans. I'm happy with my DigitalOcean droplets, but I'm curious.
@wdkevo They do cloud/VPS/dedicated but wouldn't even look there tbh.
@bashy Thanks for the response! I didn't know they offer those. And yeah, I'm personally not too fond of GoDaddy.
I hope you find this useful, this workaround seemed to work:
the folder Public in Laravel 5.4 (the version i tried to install), must be the requested file when you hit the url www.example.com, however the core files are in the parent folder,
full path here is : /home/[USER]/public_html
copy all Laravel to that URL : /home/emadha/public_html
move all laravel core files/folders to /home/Laravel <make new directory, whatever you want>
move Laravel's 'public' folder content to: /home/emadha/public_html/
that includes the files: [js,css,index.php,.htaccess,favicon.ico,robots.txt,config.txt]
Edit the file /home/emadha/public_html/index.php (the one we moved from /public folder in laravel to /public_html in godaddy)
The index.php content (as of Laravel version 5.4.23) is :
==============================================================
<?php
/**
* Laravel - A PHP Framework For Web Artisans
*
* @package Laravel
* @author Taylor Otwell <[email protected]>
*/
/*
|--------------------------------------------------------------------------
| Register The Auto Loader
|--------------------------------------------------------------------------
|
| Composer provides a convenient, automatically generated class loader for
| our application. We just need to utilize it! We'll simply require it
| into the script here so that we don't have to worry about manual
| loading any of our classes later on. It feels great to relax.
|
*/
require __DIR__.'/../bootstrap/autoload.php';
/*
|--------------------------------------------------------------------------
| Turn On The Lights
|--------------------------------------------------------------------------
|
| We need to illuminate PHP development, so let us turn on the lights.
| This bootstraps the framework and gets it ready for use, then it
| will load up this application so that we can run it and send
| the responses back to the browser and delight our users.
|
*/
$app = require_once __DIR__.'/../bootstrap/app.php';
/*
|--------------------------------------------------------------------------
| Run The Application
|--------------------------------------------------------------------------
|
| Once we have the application, we can handle the incoming request
| through the kernel, and send the associated response back to
| the client's browser allowing them to enjoy the creative
| and wonderful application we have prepared for them.
|
*/
$kernel = $app->make(Illuminate\Contracts\Http\Kernel::class);
$response = $kernel->handle(
$request = Illuminate\Http\Request::capture()
);
$response->send();
$kernel->terminate($request, $response);
=============================================================
change those :
require __DIR__.'/../bootstrap/autoload.php';
$app = require_once __DIR__.'/../bootstrap/app.php';
to the correct path of Laravel
to:
require __DIR__.'/../Laravel/bootstrap/autoload.php';
$app = require_once __DIR__.'/../Laravel//bootstrap/app.php';
HOWEVER, these changes will cause issues with your IDE FTP client, so keep that in mind, for instance your FTP remote directory will most likley be pointing to /public_html but laravels files are located one directory behind as a work around you can set the ftp remote directory or destination directory whatever you want to call it, to point to /home/Laravel, you can play however you like from here, but that workaround just to solve the issue with laravel own directory structure, (!ON godaddy shared hosting!), changes in apache can as well solve the issue in a clean way, but i can't find that on godaddy shared hosting.
hope you find this usefull
Update:
i found this much more cleaner :)
https://laravel.io/forum/03-06-2015-how-to-setup-laravel-5-in-shared-hosting?page=1#reply-24588
Ehh you should be using a symbolic link. I originally did it the way you are taking about, but found that is inefficient and cumbersome in the future.
Have the following structure
home/{username}/public_html/ ---> ../laravel-application/public
The public_html folder, the whole thing, would simply be a symbolic link to your public folder in your Laravel application.
I have a GoDaddy shared hosting plan using Laravel 5.4 and I couldn't be happier. For those who think GoDaddy is bad... why? I have the lowest shared hosting plan available and I have 99.97% up time (based on up time robot pinging ever 5 minutes for the past three months, and the .03% was when I pushed fault code that broke the server) The only thing I'm sad about is GoDaddy's shared hosting plan offers php 5.6.25, and Laravel 5.5 is moving to 7. Other than that, GoDaddy, in my opinion, is better than some of the competition.
5.5 is moving to 7
That's crazy. But what happens when only one person is in control. No backwards compatibility to help folks who have spent a lot of time programming a site. I am currently on ver 5.1 and had high hopes for ver 5.5.
I may have to look into nova framework.
@jlrdw Just stay on 5.1 then? Most code bases work fine on PHP7 anyway.
@bashy it's not the code base, it works on php 7, I have a humane society site on godaddy. But I suspect that they will have php 7 available before to long, they usually lag behind for several months.
@jlrdw If they don't, moan to them for not supporting an active PHP version :)
I have already expressed my concern with GoDaddy about their php 5.6.25 support, but laravel 5.1, 5.2, 5.3, and 5.4 have long term support.. thus I don't see the huge problem.
@gofish543 no, 5.1 is LTS, next, is 5.5. Those in between versions are not LTS. I also got with godaddy they will have seven soon but not an ETA yet.
Please or to participate in this conversation.