Piwigo.org

lorindashop · 2018-04-25 02:43:13

Hello/Hi/Greetings,

Please I upgrade my piwigo and I started having error: HTTP ERROR 500 on my page. so anytime I enter: www.lorindashop.com on the browser, then it change to http://www.lorindashop.com/upgrade.php

but this is the error I am receiving: This page isn’t working
www.lorindashop.com is currently unable to handle this request.
HTTP ERROR 500,

I install: Piwigo Version: 2.7.4

I need help.

Thanks,

Piwigo version:2.7.4
PHP version: PHP 5.6
MySQL version: 4.7.7
Piwigo URL: http://lorindashop.com

executive · 2018-04-25 03:19:46

Please read the first topic at the top of the forum.

"READ ME: getting an error after the update?"

lorindashop · 2018-04-25 13:25:37

hello,

I read the first topic, but that can't solve my problem. Because I cannot even have access to my admin page. because when I type the http://www.lorindashop.com/admin.php?page=album- to get to my admin page, it redirect me to http://www.lorindashop.com/upgrade.php, so I cannot have access at all

executive · 2018-04-25 20:44:47

??

The first step is to manually install the update. You do not need admin access for that.

quincybatten · 2021-05-04 09:10:44

The error is too generic and does not tell you exact problem. What you need is to find out what is the real issue. If your site is serving a Internal Server Error, this can be caused by a number of things, such as:

Errors in .htaccess files
Server permission
Server timeout
Script timeout
Or some other Web Server Issues
Normally, a permissions issue on the file (or files) would be one cause of the 500 Internal Server Error . The simple solution is to run chmod 644 on the problem file(s) or chmod 755 on the directories.

$ sudo chmod -R 777 /"your files location"

The best way to debug the error depends upon the server and what’s actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.

erAck · 2021-05-04 14:11:13

A global chmod 777 is always a bad idea and ill-advised. To achieve 755 (drwxr-xr-x) on directories and 644 (-rw-r--r--) on files recursively use

Code:

chmod -R a-x,u=rwX,go=rX /path-to-piwigo

However, if the files are owned by a different ssh/ftp user than the webserver user and shall be upgradable/writable by the webserver then it should probably be 775 and 664 instead. So

Code:

chmod -R a-x,ug=rwX,o=rX /path-to-piwigo

Giving "other" (than owner user and group) write permissions is never a good idea unless it's a weird server setup. And executable bits on general files is completely useless if not dangerous.

If the web server user is owner then even read permissions for other may not be needed, so this for 750/640 could be sufficient

Code:

chmod -R a-x,u=rwX,g=rX,o= /path-to-piwigo

Similar if web server user is in group, for 770/660

Code:

#chmod -R a-x,ug=rwX,o= /path-to-piwigo

Additionally, if you want to use some tools coming with Piwigo, after that global chmod you may want to give them executable permissions again like

Code:

chmod ug+x /path-to-piwigo/tools/*.{pl,sh}

Piwigo.org

Announcement

#1 2018-04-25 02:43:13

Http Error 500

#2 2018-04-25 03:19:46

Re: Http Error 500

#3 2018-04-25 13:25:37

Re: Http Error 500

#4 2018-04-25 20:44:47

Re: Http Error 500

#5 2021-05-04 09:10:44

Re: Http Error 500

#6 2021-05-04 14:11:13

Re: Http Error 500

Code:

Code:

Code:

Code:

Code:

Board footer