I have a problem with an existing installation - especially with Nextcloud.
Nethserver is quite new… I created a user for usage with e-mail and Nextcloud. The user worked several weeks, several PCs were synchronized. All clients are installed with the current Nextcloud client from the Nextcloud website.
And when I try to logon, the error message with not trusted domain appears in the web browser.
I’m not sure, what to specify here… I added the domain, to which I try to connect: myhost.dyndns.info … and I tried to add the IP address of the client. The problem with the client(s) is, that they come out of different networks. Several offices try to connect to a central Nextcloud server.
If you’re looking for help, a bit more info would help… What kind of server is this running on? Obviously not virtualized on a decent Hypervisor like Proxmox - or you wouldn’t be having this issue. A simple rollback to the last backup would suffice…
Do you have any Backups, especially of the time the server went astray?
One good chance you have is to restore a configuration backup of the server. This does not risk any data (keeps the latest) but reset’s the configuration back to what was working.
→ You could even delete Nextcloud from Software Center, and let configuration backup restore that…
As to your question: I do have clients who log in to their mail and Nextcloud from all over - all without any issues. But you must use a valid SSL certificate, for example the free LetsEncrypt, which I’m using for ALL my clients!
And also: about 40% of my clients have a dynamic IP, and use DynDNS. The real Domain is pointing to the DynDNS name, so we have our own valid domain and correct ssl certs, despite the Ips changing once in a while or even daily!
It’s worth the little work, to get stable working, and satisfied clients!
thank you very much… I “solved” the one problem… I think it was an incorrect entry in the trusted_domains setting in config.php… and created a new problem
In the nethserver web interface I did an update on Nextcloud (and also applied all other updates). When I now go to the webpage https://myserver.dyndns.info/nextcloud, then a page is displayed where I am asked to update to version 22.2.0 . When I click on “Update” at the bottom, the message appears: “Exception: Updates between multiple major versions and downgrades are unsupported.”
I also tried “occ upgrade” on a console. This did not work either. “occ status” said:
I think I have a mixture of installations now… also the data is spread in different directories: the “old” data from the clients that I already connected is located in /var/lib/nethserver/nextcloud/.
After I did the “update” or whatever I did: the new user’s data is located in /usr/share/nextcloud/data/.
I’m really unsure, how I can get rid of that version mix and distributed data…
No, it is not working, the clients can not connect… and when I click on the “Nextcloud” link in Nethserver web interface I get to the screen where it says, that I should update to version 22.2.0. I have to do something unfortunately.
The same version is in the config.php… which looks “destroyed”… compared to a config.php on a former version on a different Nethserver. In the former version there is dbuser and password, which is not in the damaged version any more.
The systemctl command further on top of your link (systemctl -l status rh-php73-php-fpm firstname.lastname@example.org) shows that both are “active (running)”.
I’m not sure, which is the better way: to deinstall and try to get the data back in somehow… or to try and perform the downgrade from the wiki… if I understand the downgrade correctly, then I’d have to downgrade only to nethserver-nextcloud-1.16.6-1.ns7.noarch as it is mentioned at the beginning of “yum history”, and not to “nextcloud-16…”
You had nethserver-nextcloud-1.16.6-1.ns7.noarch (Nextcloud 20.0.8) and updated to 1.19.0-1.ns7.noarch (Nextcloud 22.2.0) so jumped over (skipped) one major release (Nexcloud 21.x) which could be, for instance nethserver-nextcloud-1.17.1-1.ns7.noarch (Nextcloud 21.0.3) according to the package changelog.
As pointed by Andy, usually the data remains (/var/lib/nethserver/nextcloud/), and also the database (in another path) which holds other settings/data than documents. The dbuser is commonly nextcloud, the dbpassword shall be found at /var/lib/nethserver/secrets. If all of the above is present, you could rename the bad config.php file (and restore it from a backup if you can) and then do a downgrade to nethserver-nextcloud-1.17.1-1.ns7.noarch, unless I’m missing something else.
it’s me again… I could not work on my problem last week, so it still exists…
If I understand Marc / the wiki correctly, I should get a correct config.php, which was not easy… I modified it manually. At the moment there is an “Internal Server Error” when I open the Nextcloud page in a web browser.
A backup of the nextcloud directories in /usr/share and /var/lib/nethserver is running… and now I should perform a downgrade? I’m not sure about the version number…
And second question if that does not work: Andy said to deinstall nextcloud in the Software Center… but it is not there. In the main screen I saw 26 applications but now Nextcloud… then I clicked on “Reload”, the cache was cleared… and now I have zero applications???
OK, I’m trying to remember where we left of the other time…
If the config file is complete it is possible that it prevents the new version of nextcloud to connect to the database due to changes in underlying mariadb version on how nextcloud connects to it.
First, we can try to check if with the update the database was moved/imported to a new instance.
# listing related database services
systemctl | grep mariadb
systemctl | grep mysqld
# checking status of new mariadb version used by nextcloud
systemctl status -l email@example.com
# list of databases on new mariadb instance
# list of databases on old mariadb instance
# list of database users on new mariadb instance
/opt/rh/rh-mariadb105/root/bin/mysql --socket="/var/run/rh-mariadb105-mariadb/nextcloud-mysql.sock" -e 'SELECT user FROM mysql.user'
# list of database users on old mariadb instance
mysql -e 'SELECT user FROM mysql.user'