Hello everyone? Are you all doing well?
Every time I start my processes, I occasionally encounter a display error. What could be causing this?
Configurations in the n8n server and baserow together:
- 32 GB RAM / 4 cores
- Virtual machine
- +2 Ghz Frequency
- Separate docker environment
Thanks a lot
Information on your n8n setup
- n8n 0.225.2
- Database using:Baserow
- Running n8n with the execution process [own(default), main]:own
- Running n8n via [Docker, npm, n8n.cloud, desktop app]:Docker
Have you checked the docker output? The error looks like n8n probably isn’t running so it would be worth making sure it is started and that there are no errors.
We also don’t support Baserow as a backend database for the application itself, Are you using the default database?
Yes, I checked the logs in docker, and there are some errors on the processes, so does it cause the temporary cut on the browser?
Yes, I used the default database, but Baserow is just a database used in the process.
It depends on what the errors are that you are seeing, It could be that the browser is crashing because there is too much data or it could be that n8n is having a hard time.
If it’s the browser that handles a lot of data and causes this error, is N8N still running in the background and the process still terminates correctly?
It should do yeah, but that depends on if it is the browser or n8n. I don’t know what the translation for that error is or what you are seeing in the n8n log though.
Thanks a lot @Jon , it’s a client-side problem with the browser, it doesn’t support a lot of data, and long processing, so I have to optimize my process