Hello @lucasreis ,
Could you please share further information about your problem and workflow?
Thanks
Yes, please help also provide if you are cloud n8n or self hosting. Many thanks
This error appears frequently. I’ve tried to resolve it by reconfiguring the Docker file. I’ve done everything possible, and so far I haven’t been able to resolve this error. I did a more in-depth analysis and it told me that the CDN n8n.iostatic is down. But to be honest, I don’t think that’s the case. If not, I would receive some information from everyone here on the forum.
My installation is a VPS from Hostinger. I installed the entire Web Server system (Nginx), configured Firewall (UFW), and also SSL (Let’s Encrypt with Certbot). The goal is to make n8n work with my domain and I managed to do it, but this error keeps appearing at the same time.
1 Like
Hello,
Yes, you’re right, I’ve done it recently and it’s working all okay, it could be based on location, though I’ve seen this issue before where n8n blocks certain locations.
You can disable these also, which may help Isolate n8n | n8n Docs that might help isolate any unnecessary calls.
The n8n selfhosted server does need to connect outside, though, to activate. Is it always the activation you have issues with?
Best regards,
Samuel
Do you get this error all the time?
actually when i start n8n on the vps, i installed it yesterday and until now i’m racking my brains lol now it appears all the time, anywhere to click
Ah, can you redeploy? I can help if you like.
I would be checking if another instance does it with same template.
@lucasreis Hope you get resolved soon.
Samuel