-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config.php lost during upgrade #18973
Comments
|
Hm I don't know. Someone here pointed out that pacman should not be touching |
So I gave it a quick test on my Arch laptop. Actually all seemed to have worked out allright, although I did not have nextcloud really running, just tested the install/update process. I've installed the 17.0.2 package, created a config.php file in the symlinked
but there was no 17.0.3 version of the nextcloud package, so I presume you mean the stable 18.0.0 version, right? |
Ah sorry, it was 17.0.1 -> 17.0.2 actually. |
So a quick check of the up 17.0.1 -> 17.0.2 upgrade, behaves fine too. The same way as the 17.0.2 -> 18.0.0 upgrade, config.php file is not touched and kept in place. |
Yes, when doing the upgrade the new php got installed too and then nextcloud complained about it, so technically the php version I had while config.php was replaced was 7.4.1. Only after that did I downgrade php again |
#18978 Just to mention it. It's probably not related to this security hardening. Actually we should not create Lines 242 to 243 in d05f131
If
Place it next to index.php (or console.php) and access the file via your webserver. |
Is this Issue still valid in NC21.0.2? If not, please close this issue. Thanks! :) |
Doesn't seem so :) At least it has not happened to me again. I'll close |
Steps to reproduce
I didn't try to reproduce.
What happened is that after letting pacman update the packages from 17.0.1 to 17.0.2, it also updated php to 7.4.1, which nextcloud was not compatible with, and nextcloud complained. So I downgraded back to 7.3.12. Then when visiting the home page of my nextcloud installation, it did not ask to perform the upgrade, but to 'install nextcloud' and fill in the database name etc. Turns out the reason was that at some point
/etc/webapps/nextcloud/config/config.php
(which on arch is symlinked to/usr/share/webapps/nextcloud/config/config.php
) has been replaced by a stub, see config report below. Here are the timestamps.ls --full-time
/var/log/pacman.log
So I can't say if
config.php
got replaced during the php-update or the nextcloud-update.I had no backup but I could make nextcloud run again by rewriting
config.php
by hand.According to them its not
pacman
s fault.maybe related:
Expected behaviour
Settings in
config.php
should not change after update.Actual behaviour
config.php
got replaced by one that contains nothing but aninstanceid
.Server configuration
Operating system:
arch
Web server:
nginx 1.16.1
Database:
mariadb
PHP version:
7.3.12 / 7.4.1
Nextcloud version:
17.0.1
Updated from an older Nextcloud/ownCloud or fresh install:
updated
Where did you install Nextcloud from:
arch repository
Signing status:
Signing status
No errors since I fixed it already.
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Operating system: arch
Logs
Web server error log
Web server error log
There is nothing really before or after.
Nextcloud log (data/nextcloud.log)
Nextcloud log
I can post more logs is it makes sense.
EDIT: wrong version numbers for nextcloud and php
The text was updated successfully, but these errors were encountered: