Laravel 5.7 500 error on PHP 7.2 enviroment











up vote
-2
down vote

favorite












I have made an script using Laravel which runs smoothly on an WAMPP server with PHP 7.2. Recently, I tried to go live, but my server runs into 500 Error. My Server is running PHP 7.2 and matches the requirements listed in laravel documentation.



Now comes the real problem - There's nothing in the logs. As per my knowledge, Laravel logs errors into storage/logs but it's just blank.



What could be the reason behind it?



I am running on an Apache Server with cpanel and whm.










share|improve this question






















  • Show us the full error please.
    – Script47
    Nov 9 at 13:17










  • Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
    – DanFromGermany
    Nov 9 at 13:17








  • 1




    You'll have to check your apache logs if nothing is in storage/logs/
    – Travis Britz
    Nov 9 at 13:19






  • 1




    First look should be in the PHP log, not in Laravel or Apache log.
    – DanFromGermany
    Nov 9 at 13:19






  • 1




    @PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
    – Travis Britz
    Nov 9 at 13:23















up vote
-2
down vote

favorite












I have made an script using Laravel which runs smoothly on an WAMPP server with PHP 7.2. Recently, I tried to go live, but my server runs into 500 Error. My Server is running PHP 7.2 and matches the requirements listed in laravel documentation.



Now comes the real problem - There's nothing in the logs. As per my knowledge, Laravel logs errors into storage/logs but it's just blank.



What could be the reason behind it?



I am running on an Apache Server with cpanel and whm.










share|improve this question






















  • Show us the full error please.
    – Script47
    Nov 9 at 13:17










  • Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
    – DanFromGermany
    Nov 9 at 13:17








  • 1




    You'll have to check your apache logs if nothing is in storage/logs/
    – Travis Britz
    Nov 9 at 13:19






  • 1




    First look should be in the PHP log, not in Laravel or Apache log.
    – DanFromGermany
    Nov 9 at 13:19






  • 1




    @PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
    – Travis Britz
    Nov 9 at 13:23













up vote
-2
down vote

favorite









up vote
-2
down vote

favorite











I have made an script using Laravel which runs smoothly on an WAMPP server with PHP 7.2. Recently, I tried to go live, but my server runs into 500 Error. My Server is running PHP 7.2 and matches the requirements listed in laravel documentation.



Now comes the real problem - There's nothing in the logs. As per my knowledge, Laravel logs errors into storage/logs but it's just blank.



What could be the reason behind it?



I am running on an Apache Server with cpanel and whm.










share|improve this question













I have made an script using Laravel which runs smoothly on an WAMPP server with PHP 7.2. Recently, I tried to go live, but my server runs into 500 Error. My Server is running PHP 7.2 and matches the requirements listed in laravel documentation.



Now comes the real problem - There's nothing in the logs. As per my knowledge, Laravel logs errors into storage/logs but it's just blank.



What could be the reason behind it?



I am running on an Apache Server with cpanel and whm.







php laravel






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 9 at 13:08









Pratik Patil

1




1












  • Show us the full error please.
    – Script47
    Nov 9 at 13:17










  • Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
    – DanFromGermany
    Nov 9 at 13:17








  • 1




    You'll have to check your apache logs if nothing is in storage/logs/
    – Travis Britz
    Nov 9 at 13:19






  • 1




    First look should be in the PHP log, not in Laravel or Apache log.
    – DanFromGermany
    Nov 9 at 13:19






  • 1




    @PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
    – Travis Britz
    Nov 9 at 13:23


















  • Show us the full error please.
    – Script47
    Nov 9 at 13:17










  • Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
    – DanFromGermany
    Nov 9 at 13:17








  • 1




    You'll have to check your apache logs if nothing is in storage/logs/
    – Travis Britz
    Nov 9 at 13:19






  • 1




    First look should be in the PHP log, not in Laravel or Apache log.
    – DanFromGermany
    Nov 9 at 13:19






  • 1




    @PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
    – Travis Britz
    Nov 9 at 13:23
















Show us the full error please.
– Script47
Nov 9 at 13:17




Show us the full error please.
– Script47
Nov 9 at 13:17












Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
– DanFromGermany
Nov 9 at 13:17






Hi Pratik and welcome to Stackoverflow! The thing with error 500 is, that you can lookup the problem in the log files. Everything else is just guessing. Developers don't play guessing games when they know the error is written in a log file!
– DanFromGermany
Nov 9 at 13:17






1




1




You'll have to check your apache logs if nothing is in storage/logs/
– Travis Britz
Nov 9 at 13:19




You'll have to check your apache logs if nothing is in storage/logs/
– Travis Britz
Nov 9 at 13:19




1




1




First look should be in the PHP log, not in Laravel or Apache log.
– DanFromGermany
Nov 9 at 13:19




First look should be in the PHP log, not in Laravel or Apache log.
– DanFromGermany
Nov 9 at 13:19




1




1




@PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
– Travis Britz
Nov 9 at 13:23




@PratikPatil there must be an apache log. By default it would be in /var/log/apache2/error.log
– Travis Britz
Nov 9 at 13:23












1 Answer
1






active

oldest

votes

















up vote
0
down vote













Make sure your web server has writing privileges to the /storage folder and all its sub-folders. I always have this problem when creating a new application.






share|improve this answer





















  • Cross checked, 0755 Permission is set :-)
    – Pratik Patil
    Nov 9 at 13:15










  • @PratikPatil with what owner/group?
    – Travis Britz
    Nov 9 at 13:25











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53226317%2flaravel-5-7-500-error-on-php-7-2-enviroment%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













Make sure your web server has writing privileges to the /storage folder and all its sub-folders. I always have this problem when creating a new application.






share|improve this answer





















  • Cross checked, 0755 Permission is set :-)
    – Pratik Patil
    Nov 9 at 13:15










  • @PratikPatil with what owner/group?
    – Travis Britz
    Nov 9 at 13:25















up vote
0
down vote













Make sure your web server has writing privileges to the /storage folder and all its sub-folders. I always have this problem when creating a new application.






share|improve this answer





















  • Cross checked, 0755 Permission is set :-)
    – Pratik Patil
    Nov 9 at 13:15










  • @PratikPatil with what owner/group?
    – Travis Britz
    Nov 9 at 13:25













up vote
0
down vote










up vote
0
down vote









Make sure your web server has writing privileges to the /storage folder and all its sub-folders. I always have this problem when creating a new application.






share|improve this answer












Make sure your web server has writing privileges to the /storage folder and all its sub-folders. I always have this problem when creating a new application.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 9 at 13:12









Jerodev

16.5k84169




16.5k84169












  • Cross checked, 0755 Permission is set :-)
    – Pratik Patil
    Nov 9 at 13:15










  • @PratikPatil with what owner/group?
    – Travis Britz
    Nov 9 at 13:25


















  • Cross checked, 0755 Permission is set :-)
    – Pratik Patil
    Nov 9 at 13:15










  • @PratikPatil with what owner/group?
    – Travis Britz
    Nov 9 at 13:25
















Cross checked, 0755 Permission is set :-)
– Pratik Patil
Nov 9 at 13:15




Cross checked, 0755 Permission is set :-)
– Pratik Patil
Nov 9 at 13:15












@PratikPatil with what owner/group?
– Travis Britz
Nov 9 at 13:25




@PratikPatil with what owner/group?
– Travis Britz
Nov 9 at 13:25


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53226317%2flaravel-5-7-500-error-on-php-7-2-enviroment%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Landwehr

Reims

Schenkenzell