when you go to the login page what do you see? is the error coming from apache or php?

Right now I get a different message from apache2 error log. But then again I have been editing some stuff in apache2 main configuration file and sites enabled.

This is what I get now: [:error] [pid 20865] [client ...] script '/var/www/laravel/public/wp-login.php' not found or unable to stat

Before I got the landing page to work the apache error log clearly said DENY, and now it's like this. Do you think maybe the problem is in Laravel, and by that I mean some configuration issue in /config or /public?

I get several different errors (apache2 error log). Most recent: core error Invalid URI in request

Also, I set this to true to try and further detect where laravel screws up:

/*
|--------------------------------------------------------------------------
| Application Debug Mode
|--------------------------------------------------------------------------
|
| When your application is in debug mode, detailed error messages with
| stack traces will be shown on every error that occurs within your
| application. If disabled, a simple generic error page is shown.
|
*/

'debug' => env('APP_DEBUG', true),

Your error is with your apache/server config, not a laravel problem

Why does your log report "wp-login.php" - this doesn't look like a laravel request

Some type of rewrite issue perhaps, but that reference to 'wp-login.php' def. should not be there at all. Do you have the .htaccess file that laravel came with in public?

Yea, I'm beginning to suspect "wp-login.php" has nothing to do with Laravel at all.

The .htaccess-file in the /public directory is untouched.

RewriteEngine On

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

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

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

Do I have to install git to get laravel to work?

And one more thing: this line: sudo chgrp -R webmasters /var/www/html

What does it do? I mean I suspect it creates a www-group - a list of users that grants the permission to create files (and change) in the www-directory (/var/www/html). Laravel should work without defining this group?

Is there anything in the main apache2.conf -file i need to edit? Is this correct?

Sets the default security model of the Apache2 HTTPD server. It does

not allow access to the root filesystem outside of /usr/share and /var/www.

The former is used by web applications packaged in Debian,

the latter may be used for local directories served by the web server. If

your system is serving content from a sub-directory in /srv you must allow

access here, or in any related virtual host.

<Directory /usr/share> AllowOverride None Require all granted </Directory>

<Directory /var/www/> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory>

#<Directory /srv/>

Options Indexes FollowSymLinks

AllowOverride None

Require all granted

#</Directory>

The above post doesn't look at all as I wrote it, seems like this forum escapes line-breaks at random.