Shared Hosting without SSH and Laravel

Level 65

GoDaddy have no SSH or log viewing functionality on shared hosting? Knew the company was bad but...that's basic stuff.

Logs would tell you everything. Apache (which I assume they're using) would log the error for either misconfigured htaccess file or something related. Is there no log files in the main login for the control panel?

1 like

Penderis

Level 3

Yeah it is tricky without knowing what they changed on the server but in shared hosting I have never had that they actually change the public folders name for me , it usually public_html then offline I make sure I mirror this , so would have root/ then your app files with public renamed to public_html to replace their public_html folder which is already setup so apache knows . My only question could be are you putting public inside public_html or whatever your public folder for the site is? since your public folder must be the main one.

and having the same folder structure offline you can debug before uploading. I also have shared hosting on apache, and my solution always has been to just change my public folder name to whatever my servers is on my local machine and test paths.

Have you asked them for jailed access to ssh?

1 like

Level 1

I did eventually find logs but I had to manual turn them on and they don't start recording until 24 hours after you turn them on and they only persist for 7 day before being automatically deleted, so I might have to just wait another 19 hours to figure out what's going on.

And the plan my client has allows them to make multiple folders and associate them with domain names. ex site.com would correspond with the /site folder. So I was able to make myapp.com load from the /myapp/public folder. If that makes sense.

And sadly no access to ssh.

Thanks for the help and ideas.

Level 19

You do have the .htaccess file in the public folder don't you? And rewrite is enabled for the virtual host?

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Redirect Trailing Slashes...
    RewriteRule ^(.*)/$ /$1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

1 like

Level 1

Yes, I have the .htaccess in the public folder that is exactly like you posted.

Also I believe so, there are other Wordpress installs on the same server that use the .htaccess file for rewrite rules.

Level 19

Just out of interest, try commenting out the lines below for mod_negotiation. I've not seen that requirement before.

<IfModule mod_rewrite.c>
    # <IfModule mod_negotiation.c>
        Options -MultiViews
    # </IfModule>

    RewriteEngine On

    # Redirect Trailing Slashes...
    RewriteRule ^(.*)/$ /$1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

1 like

Level 1

Thanks for the idea but it didn't have any affect.

Still able to load the '/' page without any issue but any other route continues to return a GoDaddy 500 server error.

Best Answer

Level 19

Ok, one last idea, if your site is within a sub-folder, try adding RewriteBase like below. Play around with the sub-folder too, maybe you need something like /my-sub-folder/public/. Just an idea.

    # ...
    RewriteEngine On
    # add here
    RewriteBase /my-sub-folder/  
    # ...

EDIT... another thing I found is that some people suggest adding a forward slash before the index.php part:

RewriteRule ^ /index.php [L]

1 like

Level 1

THAT WAS IT!!!

The '/' before RewriteRule ^ /index.php [L]

Wow, I can't belive it was that. Thanks so much @sitesense for your help.

Level 19

Excellent :)

1 like

joginder89