500 Error on al routes but '/' Laravel 8

@mikepage its entirely likely that 777 is your problem.

directories should be 755. your ISP may block you from having 777 on directories as its a security risk.

individual files should be 644

Changed the permissions. Still have the issue Sorry

@mikepage probably worth raising a support ticket with ionos 1&1 as they'll be able to check your servers error log.

if the / route works fine, add a log entry into this page to prove that your logging works.

What's your route file? Can you share it? We can't help you with nothing. Remember that the route "format" has changed on Laravel 8.

Here are my routes:

Route::get('/', [BodyStatsController::class, 'index'])->name('body_stats.index');

Route::post('/result', [BodyStatsController::class, 'result'])->name('body_stats.result');

Route::post('/save', [BodyStatsController::class, 'save'])->name('body_stats.save');

So only post routes? What if you add another get route?

Route::get('/foo', [BodyStatsController::class, 'index'])->name('foo');

Hi I have added a log entry and it is working fine.

@sinnbeck Just added a get and still got the 500

Is there a htacces file in the public folder? Can you share its contents? And consider asking your host if mod_rewrite is enabled on the server (if apache)

Here it the .htacces in the public folder

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

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

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

Do you mean .htaccess?

@sinnbeck Yes I did. Edited

Ok, that looks perfectly fine. My best bet is that mod_rewrite isn't enabled or the virtual host config is wrong. Contact the provider like @automica suggested

Does the 500 error look like a Laravel page?

It would be unusual for the framework to issue a 500 error and not be able to write anything to the logfile.

Perhaps your webserver itself is generating the 500 error?

@sinnbeck

I'm going to give them a call today. The only thing that is making me think it's not the sever, is that I am getting the same problem on AWS and Digital Ocean to.

Can you post a screenshot of the 500 error page, so we can see if it is laravel or server that throws it?

@snapey

Its not a Laravel page.

Ok, then they can probably check the server logs for the error :)