Note that you might not be running as user www-data or apache. $ sudo chown -R apache /path/to/laravel/files $ sudo chown -R www-data /path/to/laravel/files On Ubuntu/Debian servers, your PHP may be running as user "Make sure your files are owned by the user that is running PHP: # Debian/Ubuntu I've always solved this by making the app/storage directory writable by Apache (either group writable to "www-data", "apache" or world-writable - that depends on your server setup. Since upgrading to Laravel 4.1, I've had white screen "errors" (WSOD) when the application could not write to the log location. LaravelĪre you checking Laravel's logs or Apache's logs? PidFile: "/usr/local/apache2/logs/httpd.pid"ĭoes this answer describe or help your situation? Upgrading to Apache 2.4 come with some changes in Apache configuration. Mutex default: dir="/usr/local/apache2/logs/" mechanism=default Main ErrorLog: "/usr/local/apache2/logs/error_log" Enable Automatic screen sharing to automatically share scree n content with. Enter the Exchange sign-in credentials (if different from the credentials entered. Select the check box to agree to the software license terms and acknowledge. Port * namevhost (/usr/local/apache2/conf/extra/httpd- nf:34) The Setup screen is displayed on the control device. Port * namevhost (/usr/local/apache2/conf/extra/nf:25) Heres my virtual host directive: DocumentRoot "/var/sites/laravel/public"Īnd apachectl -S $ /usr/local/apache2/bin/apachectl -Sĭefault server (/usr/local/apache2/conf/extra/nf:25) htaccess: $ cat /var/sites/laravel/public/.htaccess htaccess is loading as I get a 500 when I insert an invalid line to /var/sites/laravel/public/.htaccess. Now I'm getting a white blank screen when I go to, nothing in apache error logs, routes and etc. My laravel site was working before, I recently upgraded to Apache 2.4 and PHP 5.5.7.
0 kommentar(er)
