Sounds like a permissions issue. When you set up your cron job, what user executes the task?
If you set up the cron as root for example, the root user would create a new laravel.log owned by root.root. Then, when you hit your site it's running as the apache user, and that user wouldn't be able to write to laravel.log due do the permissions.
Confirmed! that was the issue. Making some research I found this: http://stackoverflow.com/questions/27674597/laravel-daily-log-created-with-wrong-permissions
So I applied this awesome and very clean solution: http://laravel.io/forum/06-02-2015-putting-os-username-into-log-file-name
Thanks @joetito1 for your time and for bringing me some light into this!
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast