Before asking for help please read "How to request help" by clicking on that tab above here.
  • Page:
  • 1

TOPIC: Auto Update for 2.0.3 caused site to get 500 error

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #1

  • kevyNC
  • kevyNC's Avatar Topic Author
  • Offline
  • New
  • New
  • Posts: 50
Not sure what went wrong -- everything appeared to work fine with the Auto Update from the control panel
This was worked for every 2.0.x update previously.
After I hit continue -- I could not access the WebTree site at all -- I was getting a 500 error at one point. I thought it might be related to my .htaccess file in the WebTrees folder
Also WebTrees is installed as a "subsite" in a folder of the main site so I am not sure if that was part of my issue. Just was trying to figure out what went wrong....
Everything was green before I hit continue.

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #2

Please check the webserver log, the information you provided cannot directly determine where the problem is.
In addition, manual update is recommended.
Wang Family Website of Suining County, China
https://www.snwsjz.com
A family tree website that is customized, more humanized and convenient for users.

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #3

  • kevyNC
  • kevyNC's Avatar Topic Author
  • Offline
  • New
  • New
  • Posts: 50
Yes -- I manually updated and moved to a new subdirectory. I just wondered if anyone had that experience and how to resolve it other than manual update.

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #4

  • kevyNC
  • kevyNC's Avatar Topic Author
  • Offline
  • New
  • New
  • Posts: 50
ps. I suspect it may have been a file (or folder) in the modules 4 directory...not sure which one. I

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #5

Automatic upgrade failed, usually due to file or folder permissions.
Wang Family Website of Suining County, China
https://www.snwsjz.com
A family tree website that is customized, more humanized and convenient for users.

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #6

  • kevyNC
  • kevyNC's Avatar Topic Author
  • Offline
  • New
  • New
  • Posts: 50
ALso I found this when trying to reinstall the custom Fan Chart

[19-Mar-2020 02:03:52 UTC] PHP Fatal error: Class MagicSunday\Webtrees\AncestralFanChart\Module contains 6 abstract methods and must therefore be declared abstract or implement the remaining methods (Fisharebest\Webtrees\Module\ModuleChartInterface::chartBoxMenu, Fisharebest\Webtrees\Module\ModuleChartInterface::chartMenu, Fisharebest\Webtrees\Module\ModuleChartInterface::chartMenuClass, ...) in /home1/alveslab/public_html/wt_2.0.3/modules_v4/webtrees-fan-chart/src/Module.php on line 24

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #7

  • JLL
  • JLL's Avatar
  • Offline
  • New
  • New
  • New user Webtrees 2.0.1 / 2.0.2 /2.0.3
  • Posts: 2
Hello!
I also have the same problem as kevyNC.
Error 500!
The installation of version 2.0.3 went smoothly without any errors. except ERR 500.
I do not have enough knowledge to act alone: I do not know how to manually resume the operation: can you help me on this subject because now I am completely blocked!
My hosting site is PlanetHoster and I am very satisfied with it automatically offering me the new version to download, which I did ....... unfortunately!
Thank you in advance for your assistance !
Jean-Luc


Attachments:

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #8

  • kevyNC
  • kevyNC's Avatar Topic Author
  • Offline
  • New
  • New
  • Posts: 50
try UNINSTALLING all module 4 items (disabling may work). When I did that it -- I no longer received the error -- I installed an older version of 2 of the items and it now is working -- not sure if there is a conflict or maybe something left over in one of the files.

Please Log in or Create an account to join the conversation.

Do you need a web hosting solution for your webtrees site?
If you prefer a host that specialises in webtrees, the following page lists some suppliers able to provide one for you: 

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #9

  • fisharebest
  • fisharebest's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 12929
Greg Roach - This email address is being protected from spambots. You need JavaScript enabled to view it. - fisharebest.webtrees.net

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 months 1 week ago #10

  • JLL
  • JLL's Avatar
  • Offline
  • New
  • New
  • New user Webtrees 2.0.1 / 2.0.2 /2.0.3
  • Posts: 2
Indeed, by moving the active files of the V4 add-ons, the error 500 no longer exists!
Thanks for the help, I realize the importance of this forum!

Jean-Luc

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 weeks 2 days ago #11

Is there a list somewhere of what permissions should be for automatic upgrade?

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 weeks 1 day ago #12

  • fisharebest
  • fisharebest's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 12929
The issue is not "file permissions", but "file ownership".

There are two user accounts on your server.

One owns the files.
This is almost always your own personal account.

The other is used to run PHP scripts.
On some servers, this is an un-privileged user (typically called "www-user", "www-data", etc.)
On others, it is the same as your personal account.

So, if PHP scripts run as an unprivileged user, then they cannot overwrite files owned by you.
But if they run as your own user, then yes they can.

During installation, webtrees tests if it can write to the folder /data

If yes (because PHP is running as you), then it just carries on,

If no (because PHP is running as an unprivileged user), then it asks you to change the permissions of this folder to "777" - which means make it writable by any account on the server.

So, if you were prompted to change the folder permission to 777, then you cannot use the auto-upgrade.
If you weren't, then yes you can.
Greg Roach - This email address is being protected from spambots. You need JavaScript enabled to view it. - fisharebest.webtrees.net

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 weeks 1 day ago #13

Apologies, I should have been more explicit. My /data folder is owned and writeable by www-data but the rest of the webtrees installation is owned by the webtrees user account. Is that the way it should be for auto upgrade to work? Or does the entire webtrees installation need to be owned by www-data?

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 weeks 1 day ago #14

  • fisharebest
  • fisharebest's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 12929
> Or does the entire webtrees installation need to be owned by www-data?

So your PHP scripts are executed by www-data - which cannot overwrite the application files because it does not own them.

So, to enable auto-upgrade, just change the ownership. e.g. "chown -R www-data:www-data /path/to/webtrees"

Note that for many sites, the use of www-data is a deliberate security feature. Changing the ownership means that *any* website on the server can overwrite the webtrees scripts. Do you have other websites on the server? Do you trust them?

Personally, I would always run php-fpm (which runs scripts as the owner of the file), and then create a different user-account for each website/application. It provides much stronger isolation between sites. For example, if all sites run as www-data, then they can all read each others config files (e.g. for database credentials).
Greg Roach - This email address is being protected from spambots. You need JavaScript enabled to view it. - fisharebest.webtrees.net

Please Log in or Create an account to join the conversation.

Auto Update for 2.0.3 caused site to get 500 error 2 weeks 1 day ago #15

I'll keep that in mind for next time. Manual upgrade was a minor inconvenience but still painless.

I did not know about php-fpm. I'll be reading up on this now.

Thanks for the work you put into this. Much appreciated.

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Powered by Kunena Forum