- Posts: 115
Question upgrade issue
- philld
- Topic Author
- Offline
- Junior Member
Less
More
1 week 2 days ago #1
by philld
upgrade issue was created by philld
I have just attempted a manual upgrade from 2.1 to 2.2. After the upgrade, in the Firefox browser, I get only a blank page. In the Brave browser, I get "This page isn't working" and a HTTP Error 500. Have done the upgrade as in the past without incident. Did I miss something for the 2.2. upgrade?
Please Log in or Create an account to join the conversation.
- philld
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 115
1 week 2 days ago #2
by philld
Replied by philld on topic upgrade issue
Forgot to give system stats:
OS: Fedora 40
PHP: 8.3.13
Maria DB: 10.11.9
Web: Apache 2.4.62
OS: Fedora 40
PHP: 8.3.13
Maria DB: 10.11.9
Web: Apache 2.4.62
Please Log in or Create an account to join the conversation.
- bertkoor
- Offline
- Platinum Member
- Greetings from Utrecht, Holland
1 week 2 days ago #3
by bertkoor
stamboom.BertKoor.nl runs on webtrees v2.1.20
Replied by bertkoor on topic upgrade issue
For analysis of the cause, follow these instructions:
webtrees.net/faq/500/
With your findings from that we can go further.
webtrees.net/faq/500/
With your findings from that we can go further.
stamboom.BertKoor.nl runs on webtrees v2.1.20
Please Log in or Create an account to join the conversation.
- philld
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 115
1 week 2 days ago #4
by philld
Replied by philld on topic upgrade issue
Thanks for the guidance bertkoor. I placed the suggested commands in the .htaccess file.
When attempting to access, received the following:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Apache/2.4.62 (Fedora Linux) Server at dermottft2.duckdns.org Port 443
I then looked in the error log file, the contents of 'tail' are below.
The error log reported:
[Wed Nov 27 18:08:51.620495 2024] [core:alert] [pid 49353:tid 49376] [remote 99.249.47.15:60314] /home/admin/wwwft/webtrees/.htaccess: Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration, referer: dermottft2.duckdns.org/
[Wed Nov 27 18:09:27.761727 2024] [core:alert] [pid 49561:tid 49576] [remote 99.249.47.15:36278] /home/admin/wwwft/webtrees/.htaccess: Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration, referer: dermottft2.duckdns.org/
When attempting to access, received the following:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Apache/2.4.62 (Fedora Linux) Server at dermottft2.duckdns.org Port 443
I then looked in the error log file, the contents of 'tail' are below.
The error log reported:
[Wed Nov 27 18:08:51.620495 2024] [core:alert] [pid 49353:tid 49376] [remote 99.249.47.15:60314] /home/admin/wwwft/webtrees/.htaccess: Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration, referer: dermottft2.duckdns.org/
[Wed Nov 27 18:09:27.761727 2024] [core:alert] [pid 49561:tid 49576] [remote 99.249.47.15:36278] /home/admin/wwwft/webtrees/.htaccess: Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration, referer: dermottft2.duckdns.org/
Please Log in or Create an account to join the conversation.
- philld
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 115
1 week 2 days ago #5
by philld
Replied by philld on topic upgrade issue
It finally sunk in that the above error had to do with the code that added to the .htaccess file. For the time being, I have removed the .htaccess code and disabled all the add-ons except for the vesta modules and I am now able to login. I'll start re-enabling the add-on tomorrow one by one to see how many have a problem with the new version and have noted the possible changes that might be required as a result in how modules are called as noted in another message.
Please Log in or Create an account to join the conversation.