I didn't checked yet but manual runs of split batches stuck on last data count even if new data changed i reverted back to last version prior update all went smooth again
DualOSWinWiz
Posts
-
n8n - Package Updates -
n8n - Package Updates@nebulon update unstable do not update create problems in Split batches and other queries
-
Cloudron Backups stalling on One AppFor me this was happening on uptimekuma and i believe due to soze of data of logs for me 2 methods use to work.
- Delete logs inside uptime kuma but this was temporary and after few days it happens agains.
- Permanent solution i skipped backup of that specifi app and no problems since then
-
GitLab Upgrade ErrorYes after upgrading it solved
-
GitLab Upgrade ErrorGit Lab Update Issues
Hi Cloudron Team getting error while upgrading the Gitlab from GitLab 16.6.4 to latest version.
i restarted the system even checked all the services but its not updating below is the summary of errors. i even restarted the ubuntu server 22.04.
Database Migration Issues: The error PG::FeatureNotSupported: ERROR: DROP INDEX CONCURRENTLY must be first action in transaction suggests that there's a problem with the way a database migration is being executed. In PostgreSQL, the DROP INDEX CONCURRENTLY command must be run outside of a transaction block because it cannot be executed inside a multi-statement transaction. To resolve this, ensure that the migration script is correctly set up to execute this command outside of any transaction blocks.
File Permission Issues: The error /home/git is not writable indicates a file permission issue. The user under which the GitLab process is running does not have write access to the /home/git directory. You need to check and update the permissions of this directory to make sure that the GitLab process has the necessary access.
Repeated Health Check Errors: The Healtheck error: Error: connect ECONNREFUSED 172.18.18.240:80 suggests that GitLab is trying to connect to a service (possibly a web service or database) at 172.18.18.240 on port 80, but the connection is being refused. This could be due to the service not running, the service not listening on the expected port, network issues, or firewall rules blocking the connection.
URI Gem Warnings: The warnings about constants in the URI module being already initialized suggest that there might be conflicting versions of the URI gem, or the gem is being required multiple times in a way that causes these warnings. This might not be critical, but it's worth checking your gem dependencies and require statements to ensure there's no conflict or unnecessary duplication.
-
Encouraging Hosting Companies to Support Cloudron as an ImageCan i get a list of vps providers where Coudron is already available as working with a client and he is looking for some basic solutions and Coudron is a good base
-
Workflow execution problem with 1.21.1@nebulon Yes i confirmed all 4 n8n containers are updated and working thank you.
-
Update to 7.6.3Platform was running last night i checked all apps started i checked only few
Uptime
Guacamole
N8nI thought all good this morning someone complaint that emails are not working so do ldap taiga accounts cant login so as people were working i just restored the vm
-
Update to 7.6.3One restored back
-
Update to 7.6.3 -
Update to 7.6.3Once i restored the mirror of vm all went back to normal
-
Update to 7.6.3Yes and all user complaint they cannot access emails on platforms like Sogo, outlook, iphone , android
-
Update to 7.6.3All Email accounts went to 0 usage
Reverted back 7.6.2 and it was working -
Workflow execution problem with 1.21.1 -
Workflow execution problem with 1.21.1When i Execute a Schedule Trigger on Logs i get this error each time
Jan 03 21:03:18TypeError: moment_1.default.tz is not a function
Jan 03 21:03:40TypeError: moment_1.default.tz is not a function
Jan 03 21:04:38TypeError: moment_1.default.tz is not a function -
Workflow execution problem with 1.21.1Does anyone else faced this same problem?
-
Workflow execution problem with 1.21.1 -
Workflow execution problem with 1.21.1i posted on git as well https://github.com/n8n-io/n8n/pull/8040
-
Workflow execution problem with 1.21.1@nebulon Hi Guys this Package update cause problem with Workflows their Auto and Manual Executions are not working i have 4 n8n containers i checked on 3 and same problem i reverted back to previous version through restore and came back to normal update accordingly
-
"[EXTERNAL]" indicator for incoming emails outside of organization@girish is this function exist on cloudron?