Hi,
I’m trying to connect Xano and WeWeb.
Xano Auth plugin and REST API work fine,
but Xano plugin does not work.
I mean in workflows and when I try to add a collection, I have this error:
Network Error
I experience exactly same errors constantly. Endpoints that usually work fine give ocasionally Network Errors. You have a post that suggests that these errors are caused by XANO and gives some advices to optimise the apps, but after discussing with XANO support over the past week, optimizing endpoints, and reviewing resource usage in my XANO instance, it appears that the issue is not with XANO. In my case XANO support found no issues on their end. We even upgraded our XANO plan to scale x4, which is overkill for our app usage, as confirmed by XANO support.
Since I can’t see these errors in the request history in xano I’ve built a logger that sends a slack message with “Current Error” value in the “On Error” trigger. Here you can see few examples of the response we get on these network errors (I attached Image because weweb forum doesn’t let me post links included in the output):
This is likely Xano crying under too much load. You might check how many requests its being asked to handle in a short period of time, and how long those requests take to exit. If it is clogged with requests, it might just stop accepting new ones until it clears up.
The two parts to the equation:
Looking at how full Xano is - are there opportunities to lighten it internally? And/or do you need to upgrade your instance?
Looking at how chatty your weweb app is - are there opportunities to slow down the number of requests its sending?
As I mentioned, I spent last week optimizing my Xano endpoints and consulting with Xano support to identify the source of the errors in my instance. We upgraded to X4 scale, which is more than what our app requires. Afterward, Xano support confirmed that there are no issues on their end.
But your’e right, that in some cases it might be the problem with to many requests or not enought ressources (in most cases RAM) to handle requests, which causes XANO to deny the request. So optimizing and upgrading the xano plan might help. Unfortunatelly not in my case…
YOu might also check your own network connection. I had a problem a month ago or so where I was getting network reset errors. Turns out the wifi radio on my router was crapping out. $100 later, I was error free.
This would explain a lack of reply from Xano to your particular machine. You could test by having another, remote machine execute the test. I recently rented a server from vultr.com for the day to use the web browser from another location (in my case, testing Australia response times). It worked great, and was only a few dollars to run the test.
I installed “Xano plugin” a while ago… since this date, weweb changed it (now we have to METADATA API), but “mine” did not change properly.
I removed it and re-install… problem solved !
cc @Joyce
