Magento2 throws 500 internal server error












3















I installed Magento2.2. After installing when I visit the site, it shows




500 Internal Server Error




The same for admin section as well.



I removed my .htaccess from root folder and tried. This time around front end loads without css and js, but admin section shows




404 Not Found




Can someone help?



I referred below but no luck.



Css and admin panel not working in Magento 2 Community Edition



My Apache error log says




[Sun Jan 21 16:40:19.568718 2018] [core:alert] [pid 12172:tid 1100] [client ::1:56158] D:/wamp/www/anto/certification/magento2/.htaccess: Invalid command IfVersion, perhaps misspelled or defined by a module not included in the server configuration,











share|improve this question

























  • Please check server log. where you can get cause of it

    – Pramod Kharade
    Jan 21 '18 at 12:30











  • @PramodKharade I updated my log

    – Butterfly
    Jan 21 '18 at 12:43











  • run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

    – Pramod Kharade
    Jan 21 '18 at 12:46








  • 1





    @PramodKharade your hint helps. I need to enable mod_version in httpd.conf

    – Butterfly
    Jan 21 '18 at 12:50
















3















I installed Magento2.2. After installing when I visit the site, it shows




500 Internal Server Error




The same for admin section as well.



I removed my .htaccess from root folder and tried. This time around front end loads without css and js, but admin section shows




404 Not Found




Can someone help?



I referred below but no luck.



Css and admin panel not working in Magento 2 Community Edition



My Apache error log says




[Sun Jan 21 16:40:19.568718 2018] [core:alert] [pid 12172:tid 1100] [client ::1:56158] D:/wamp/www/anto/certification/magento2/.htaccess: Invalid command IfVersion, perhaps misspelled or defined by a module not included in the server configuration,











share|improve this question

























  • Please check server log. where you can get cause of it

    – Pramod Kharade
    Jan 21 '18 at 12:30











  • @PramodKharade I updated my log

    – Butterfly
    Jan 21 '18 at 12:43











  • run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

    – Pramod Kharade
    Jan 21 '18 at 12:46








  • 1





    @PramodKharade your hint helps. I need to enable mod_version in httpd.conf

    – Butterfly
    Jan 21 '18 at 12:50














3












3








3








I installed Magento2.2. After installing when I visit the site, it shows




500 Internal Server Error




The same for admin section as well.



I removed my .htaccess from root folder and tried. This time around front end loads without css and js, but admin section shows




404 Not Found




Can someone help?



I referred below but no luck.



Css and admin panel not working in Magento 2 Community Edition



My Apache error log says




[Sun Jan 21 16:40:19.568718 2018] [core:alert] [pid 12172:tid 1100] [client ::1:56158] D:/wamp/www/anto/certification/magento2/.htaccess: Invalid command IfVersion, perhaps misspelled or defined by a module not included in the server configuration,











share|improve this question
















I installed Magento2.2. After installing when I visit the site, it shows




500 Internal Server Error




The same for admin section as well.



I removed my .htaccess from root folder and tried. This time around front end loads without css and js, but admin section shows




404 Not Found




Can someone help?



I referred below but no luck.



Css and admin panel not working in Magento 2 Community Edition



My Apache error log says




[Sun Jan 21 16:40:19.568718 2018] [core:alert] [pid 12172:tid 1100] [client ::1:56158] D:/wamp/www/anto/certification/magento2/.htaccess: Invalid command IfVersion, perhaps misspelled or defined by a module not included in the server configuration,








magento2.2 installation permissions apache2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 21 '18 at 13:08









Pramod Kharade

1,7271028




1,7271028










asked Jan 21 '18 at 12:26









ButterflyButterfly

79342149




79342149













  • Please check server log. where you can get cause of it

    – Pramod Kharade
    Jan 21 '18 at 12:30











  • @PramodKharade I updated my log

    – Butterfly
    Jan 21 '18 at 12:43











  • run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

    – Pramod Kharade
    Jan 21 '18 at 12:46








  • 1





    @PramodKharade your hint helps. I need to enable mod_version in httpd.conf

    – Butterfly
    Jan 21 '18 at 12:50



















  • Please check server log. where you can get cause of it

    – Pramod Kharade
    Jan 21 '18 at 12:30











  • @PramodKharade I updated my log

    – Butterfly
    Jan 21 '18 at 12:43











  • run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

    – Pramod Kharade
    Jan 21 '18 at 12:46








  • 1





    @PramodKharade your hint helps. I need to enable mod_version in httpd.conf

    – Butterfly
    Jan 21 '18 at 12:50

















Please check server log. where you can get cause of it

– Pramod Kharade
Jan 21 '18 at 12:30





Please check server log. where you can get cause of it

– Pramod Kharade
Jan 21 '18 at 12:30













@PramodKharade I updated my log

– Butterfly
Jan 21 '18 at 12:43





@PramodKharade I updated my log

– Butterfly
Jan 21 '18 at 12:43













run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

– Pramod Kharade
Jan 21 '18 at 12:46







run this command and update composer once : php bin/magento setup:upgrade,php bin/magento setup:static-content:deploy , give permission check.

– Pramod Kharade
Jan 21 '18 at 12:46






1




1





@PramodKharade your hint helps. I need to enable mod_version in httpd.conf

– Butterfly
Jan 21 '18 at 12:50





@PramodKharade your hint helps. I need to enable mod_version in httpd.conf

– Butterfly
Jan 21 '18 at 12:50










3 Answers
3






active

oldest

votes


















4














As per the suggestion given by @Pramodkharade on comments, I need to enable mod_version module from my httpd.conf



Change below



# LoadModule version_module modules/mod_version.so



To



LoadModule version_module modules/mod_version.so



And the restart apache this will fix the issue.






share|improve this answer


























  • If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

    – inrsaurabh
    Jan 21 '18 at 14:26



















2














For 500 error, you need to enable mod_version in apache.



You can check all the enabled apache modules with the command apache2ctl -M. If you don't see it in the list, then it's not installed.



To do this run the command a2enmod version as the root user, or sudo a2enmod version as a non-root user and then reload apache with apache2ctl reload.



For 404 error regarding css and js, you can try changing:



Options +FollowSymLinks


to



Options +SymLinksIfOwnerMatch


in the .htaccess file located in the following locations:




  • your Magento root install directoy (this is usually the /www/ or /public_html/ folder)


  • /pub/

  • /pub/static/

  • /pub/media/






share|improve this answer


























  • Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

    – Butterfly
    Jan 21 '18 at 13:09



















0














magento2 .htaccess problem after server migration from siteground to godaddy. internal server error on image,css,js
and my website is http://mastee.in/



i have migrated from siteground hosting to godaddy. and i dont have access to any image, links, css, js files . i am guessing the problem is with .htaccess file



can anyone address what went wrong?



.htaccess file



RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot)
RewriteCond %{HTTP_USER_AGENT} !(bing|Google) [NC]
RewriteRule ^/?.*$ "http://127.0.0.1" [R,L]
# BLOCK BLANK USER AGENTS
RewriteCond %{HTTP_USER_AGENT} ^-?$
RewriteRule ^ - [F]


error with all css,images,js files



<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@mastee.boilerinstallers.london to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>





share|improve this answer
























  • the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

    – user3512810
    1 min ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fmagento.stackexchange.com%2fquestions%2f210326%2fmagento2-throws-500-internal-server-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














As per the suggestion given by @Pramodkharade on comments, I need to enable mod_version module from my httpd.conf



Change below



# LoadModule version_module modules/mod_version.so



To



LoadModule version_module modules/mod_version.so



And the restart apache this will fix the issue.






share|improve this answer


























  • If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

    – inrsaurabh
    Jan 21 '18 at 14:26
















4














As per the suggestion given by @Pramodkharade on comments, I need to enable mod_version module from my httpd.conf



Change below



# LoadModule version_module modules/mod_version.so



To



LoadModule version_module modules/mod_version.so



And the restart apache this will fix the issue.






share|improve this answer


























  • If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

    – inrsaurabh
    Jan 21 '18 at 14:26














4












4








4







As per the suggestion given by @Pramodkharade on comments, I need to enable mod_version module from my httpd.conf



Change below



# LoadModule version_module modules/mod_version.so



To



LoadModule version_module modules/mod_version.so



And the restart apache this will fix the issue.






share|improve this answer















As per the suggestion given by @Pramodkharade on comments, I need to enable mod_version module from my httpd.conf



Change below



# LoadModule version_module modules/mod_version.so



To



LoadModule version_module modules/mod_version.so



And the restart apache this will fix the issue.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 22 '18 at 5:13

























answered Jan 21 '18 at 13:07









ButterflyButterfly

79342149




79342149













  • If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

    – inrsaurabh
    Jan 21 '18 at 14:26



















  • If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

    – inrsaurabh
    Jan 21 '18 at 14:26

















If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

– inrsaurabh
Jan 21 '18 at 14:26





If @Lez answer helped you then you must mark that answer as supported rather posting as a answer.

– inrsaurabh
Jan 21 '18 at 14:26













2














For 500 error, you need to enable mod_version in apache.



You can check all the enabled apache modules with the command apache2ctl -M. If you don't see it in the list, then it's not installed.



To do this run the command a2enmod version as the root user, or sudo a2enmod version as a non-root user and then reload apache with apache2ctl reload.



For 404 error regarding css and js, you can try changing:



Options +FollowSymLinks


to



Options +SymLinksIfOwnerMatch


in the .htaccess file located in the following locations:




  • your Magento root install directoy (this is usually the /www/ or /public_html/ folder)


  • /pub/

  • /pub/static/

  • /pub/media/






share|improve this answer


























  • Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

    – Butterfly
    Jan 21 '18 at 13:09
















2














For 500 error, you need to enable mod_version in apache.



You can check all the enabled apache modules with the command apache2ctl -M. If you don't see it in the list, then it's not installed.



To do this run the command a2enmod version as the root user, or sudo a2enmod version as a non-root user and then reload apache with apache2ctl reload.



For 404 error regarding css and js, you can try changing:



Options +FollowSymLinks


to



Options +SymLinksIfOwnerMatch


in the .htaccess file located in the following locations:




  • your Magento root install directoy (this is usually the /www/ or /public_html/ folder)


  • /pub/

  • /pub/static/

  • /pub/media/






share|improve this answer


























  • Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

    – Butterfly
    Jan 21 '18 at 13:09














2












2








2







For 500 error, you need to enable mod_version in apache.



You can check all the enabled apache modules with the command apache2ctl -M. If you don't see it in the list, then it's not installed.



To do this run the command a2enmod version as the root user, or sudo a2enmod version as a non-root user and then reload apache with apache2ctl reload.



For 404 error regarding css and js, you can try changing:



Options +FollowSymLinks


to



Options +SymLinksIfOwnerMatch


in the .htaccess file located in the following locations:




  • your Magento root install directoy (this is usually the /www/ or /public_html/ folder)


  • /pub/

  • /pub/static/

  • /pub/media/






share|improve this answer















For 500 error, you need to enable mod_version in apache.



You can check all the enabled apache modules with the command apache2ctl -M. If you don't see it in the list, then it's not installed.



To do this run the command a2enmod version as the root user, or sudo a2enmod version as a non-root user and then reload apache with apache2ctl reload.



For 404 error regarding css and js, you can try changing:



Options +FollowSymLinks


to



Options +SymLinksIfOwnerMatch


in the .htaccess file located in the following locations:




  • your Magento root install directoy (this is usually the /www/ or /public_html/ folder)


  • /pub/

  • /pub/static/

  • /pub/media/







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 7 '18 at 12:37

























answered Jan 21 '18 at 12:57









LezLez

1,290729




1,290729













  • Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

    – Butterfly
    Jan 21 '18 at 13:09



















  • Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

    – Butterfly
    Jan 21 '18 at 13:09

















Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

– Butterfly
Jan 21 '18 at 13:09





Thanks for your time. Enabling mod_version.so fixed the issue. +1 for your support.

– Butterfly
Jan 21 '18 at 13:09











0














magento2 .htaccess problem after server migration from siteground to godaddy. internal server error on image,css,js
and my website is http://mastee.in/



i have migrated from siteground hosting to godaddy. and i dont have access to any image, links, css, js files . i am guessing the problem is with .htaccess file



can anyone address what went wrong?



.htaccess file



RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot)
RewriteCond %{HTTP_USER_AGENT} !(bing|Google) [NC]
RewriteRule ^/?.*$ "http://127.0.0.1" [R,L]
# BLOCK BLANK USER AGENTS
RewriteCond %{HTTP_USER_AGENT} ^-?$
RewriteRule ^ - [F]


error with all css,images,js files



<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@mastee.boilerinstallers.london to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>





share|improve this answer
























  • the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

    – user3512810
    1 min ago


















0














magento2 .htaccess problem after server migration from siteground to godaddy. internal server error on image,css,js
and my website is http://mastee.in/



i have migrated from siteground hosting to godaddy. and i dont have access to any image, links, css, js files . i am guessing the problem is with .htaccess file



can anyone address what went wrong?



.htaccess file



RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot)
RewriteCond %{HTTP_USER_AGENT} !(bing|Google) [NC]
RewriteRule ^/?.*$ "http://127.0.0.1" [R,L]
# BLOCK BLANK USER AGENTS
RewriteCond %{HTTP_USER_AGENT} ^-?$
RewriteRule ^ - [F]


error with all css,images,js files



<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@mastee.boilerinstallers.london to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>





share|improve this answer
























  • the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

    – user3512810
    1 min ago
















0












0








0







magento2 .htaccess problem after server migration from siteground to godaddy. internal server error on image,css,js
and my website is http://mastee.in/



i have migrated from siteground hosting to godaddy. and i dont have access to any image, links, css, js files . i am guessing the problem is with .htaccess file



can anyone address what went wrong?



.htaccess file



RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot)
RewriteCond %{HTTP_USER_AGENT} !(bing|Google) [NC]
RewriteRule ^/?.*$ "http://127.0.0.1" [R,L]
# BLOCK BLANK USER AGENTS
RewriteCond %{HTTP_USER_AGENT} ^-?$
RewriteRule ^ - [F]


error with all css,images,js files



<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@mastee.boilerinstallers.london to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>





share|improve this answer













magento2 .htaccess problem after server migration from siteground to godaddy. internal server error on image,css,js
and my website is http://mastee.in/



i have migrated from siteground hosting to godaddy. and i dont have access to any image, links, css, js files . i am guessing the problem is with .htaccess file



can anyone address what went wrong?



.htaccess file



RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot)
RewriteCond %{HTTP_USER_AGENT} !(bing|Google) [NC]
RewriteRule ^/?.*$ "http://127.0.0.1" [R,L]
# BLOCK BLANK USER AGENTS
RewriteCond %{HTTP_USER_AGENT} ^-?$
RewriteRule ^ - [F]


error with all css,images,js files



<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
webmaster@mastee.boilerinstallers.london to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>






share|improve this answer












share|improve this answer



share|improve this answer










answered 21 mins ago









user3512810user3512810

12




12













  • the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

    – user3512810
    1 min ago





















  • the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

    – user3512810
    1 min ago



















the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

– user3512810
1 min ago







the problem was fixed by the mod_version source -> magento.stackexchange.com/a/206042/35757

– user3512810
1 min ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Magento Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f210326%2fmagento2-throws-500-internal-server-error%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

What other Star Trek series did the main TNG cast show up in?

Berlina muro

Berlina aerponto