@girish since I recently had another issue as well, I was just thinking that maybe all this is related to the fact that I initially migrated from an older Piwik installation.
With that, I mean that after I installed the Cloudron app about 2 years ago, I imported existing data from that older Piwik installation. This might explain why I'm faced with those issues during upgrades while others aren't
guyds
Posts
-
SQL Error after Matomo was upgraded to v5.0 -
SQL Error after Matomo was upgraded to v5.0My Matomo installation was automatically upgraded to v5.0.0 and as a result a database upgrade was needed upon first access.
When I proceeded with the upgrade step, I got an Update error after several seconds:
Critical Error during the update process: /app/code/core/Updates/5.0.0-b1.php: Error trying to execute the migration 'ALTER TABLE `log_visit` ADD INDEX `index_idsite_idvisitor_time` (`idsite`, `idvisitor`, `visit_last_action_time` DESC);'. The error was: SQLSTATE[42000]: Syntax error or access violation: 1178 The storage engine for the table doesn't support descending indexes
Googling for the exact error didn't return anything useful, but by broadening my search I was able to narrow it down to a query incompatibility with the MyISAM engine, more specifically the "DESC" clause isn't supported.
So to solve the issue, I opened the MySQL cli and manually performed the query without the DESC modifier, like this:
ALTER TABLE `log_visit` ADD INDEX `index_idsite_idvisitor_time` (`idsite`, `idvisitor`, `visit_last_action_time`);
Then I restarted the upgrade procedure from the web interface and everything finished successfully.
I'm not sure if this is something that should be fixed in the Cloudron package, e.g. by upgrading to a newer MySQL version and/or switching to the InnoDB engine?
In any case, this information might be valuable for others as well.
Edit: fixed typo
-
SQL Error during login@girish, fair enough.
I definitely understand your reasoning, but on the other side there is probably a good reason why the issue was added to the Matomo FAQ -
SQL Error during loginThanks @girish, I'm glad you found the issue.
Before posting here, I did a search on the error but that didn't bring me to the Matomo FAQ. Probably my search was too specific.The question now is if/how this can be prevented in the future
For starters it might be a good idea to add this info to the documentation for the Matomo app? -
SQL Error during login@girish sure, I just sent an email to support.
-
SQL Error during loginUnfortunately, since I'm using a free version of Cloudron I can only have 2 apps on a single Cloudron and therefore I'm not in the possibility to clone from an older version because I already have another app on that same Cloudron.
And when importing a backup on another Cloudron, the versions of the old and new app should be identical and I can only install the latest version of the app on the new Cloudron, so I would only be able to clone from the latest version.Or is there a way to clone an older version of the app to another server?
-
SQL Error during loginThanks for the suggestions.
Running the migration manually doesn't have any effect though:/app/code# sudo -E -u www-data -- /app/code/console core:update --yes Everything is already up to date.
I'll try to revert to an older backup or set up a clone from an older backup
-
SQL Error during loginSuddenly I can't login anymore on my Matomo instance.
Whenever I try to login, I get the following SQL error:SQLSTATE[42S22]: Column not found: 1054 Unknown column 'login' in 'where clause'
In the Cloudron logs:
Nov 08 10:10:18[Wed Nov 08 09:10:18.623617 2023] [php:notice] [pid 225] [client 172.18.0.1:49142] [<domain-name-redacted>] Error in Matomo: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'login' in 'where clause', referer: https://<domain-name-redacted>/index.php Nov 08 10:10:1894.227.68.6 - - [08/Nov/2023:09:10:18 +0000] "POST /index.php?module=Login HTTP/1.1" 500 1733 "https://<domain-name-redacted>/index.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0" Nov 08 10:10:18172.18.0.1 - - [08/Nov/2023:09:10:18 +0000] "POST /index.php?module=Login HTTP/1.1" 500 2051 "https://<domain-name-redacted>/index.php" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0" Nov 08 10:10:20172.18.0.1 - - [08/Nov/2023:09:10:20 +0000] "GET / HTTP/1.1" 200 30862 "-" "Mozilla (CloudronHealth)"
I'm not 100% sure, but I think this happens since the latest update to 1.42.0 which includes a migration to OIDC login.
-
Cannot import app backup from other cloudron@girish Thanks!
-
Cannot import app backup from other cloudron@girish that sounds as being the same issue indeed.
So if I understand correctly you already know what the issue is and how to fix it and now it's just a matter of finding some time to actually implement it -
Hetzner Nextcloud for Backup storage?Oh, and of course you first have to install davfs2.
This can be done with the following commandsudo apt install davfs2
-
Hetzner Nextcloud for Backup storage?If you create the directory /mnt/mynextcloud and then put the following line in your /etc/fstab
https://<fqdn-of-your-nextcloud>/remote.php/dav/files/<your-username>/ /mnt/mynextcloud davfs defaults,uid=1000,gid=100,_netdev,auto 0 0
You should be able to store your backups in your nextcloud.
Automatically after reboot or manually with this command:sudo mount /mnt/mynextcloud
Note 1: you have to replace the values between <> with the correct values for your nextcloud instance and also make sure you use the correct uid and gid.
Note 2: I won't recommend this for reliable backups as it can be really slow and, well, just unreliable.
-
Cannot import app backup from other cloudron@girish said in Cannot import app backup from other cloudron:
@guyds yes, unfortunately, the fix did not make it to 7.4.
Any timeframe for when the fix will be available?
@girish said in Cannot import app backup from other cloudron:
I think https://forum.cloudron.io/topic/8672/move-local-backup-to-another-server was the same issue.
Hmmm, I'm don't see any issues mentioned in that post, it just seems to be a request for best practices regarding backups
-
Cannot import app backup from other cloudronMuch to my disappointment I just noticed that this issue still exists.
In other words, I still cannot import a backup from an sshfs location because it's still giving the errorError : External Error - Error loading fsmetadata.json:ENOENT: no such file or directory
The only way to get the app imported on a new cloudron is by manually copying over the backup to the local filesystem.
(Edit: typo)
-
Encryption error since upgrade to 25.0.2@girish Thanks, it's working again!
-
Encryption error since upgrade to 25.0.2@humptydumpty There are several alternatives indeed, such as cryptomator, but they don't solve the current issue with the Nextcloud encryption.
The only way to get access again to our Nextcloud files is by modifying the openssl config, but that's something only @girish or @nebulon can do I guess. -
Encryption error since upgrade to 25.0.2Same issue here, but I'm still on Ubuntu 20.04.
This is a major issue because we can't access any of our files anymore and we can't even apply the temporary workaround since the openssl config for the Nextcloud app is on a readonly filesystem.
Unfortunately this isn't the first time I'm experiencing issues with the server side encryption in Nextcloud
Therefore I want to turn off the encryption alltogether, but that's only possible after this issue gets fixed -
NetCup - don't use it for professional stuffNetCup can't be held responsible for the reputation of the ip address, it's simply a result of what their users have done with that ip address.
And that's something you have to keep in mind when buying servers from any provider, not only NetCup.
But that doesn't mean you can't do anything about it. In fact there is a good chance you can revert it back to a clean state just by taking the correct actions.As marcusquinn says, Hetzner is very good indeed, but their ip's aren't always clean either. They might be on some blacklists or even blocked alltogether by some parties.
I had a similar situation myself where the ip of our mailserver was blocked by Microsoft and as a result none of our emails could be delivered to microsoft addresses (hotmail, outlook, office365, ...)BUT: I contacted MS and explained the situation. After providing the necessary info / proof of ownership of the ip, they delisted the ip address and everything is fine since then.
-
Mail Certificates do not get renewed.@humptydumpty Thanks! Hadn't seen that post yet.
-
Mail Certificates do not get renewed.@girish When can we expect an update that fixes this issue?
It just happened again on one of my Cloudrons