a year ago
My API in nest is not being able to connect every minute, it keeps running and spending, it doesn't show anything in the console, and we simply can't connect to it, this happens several times a day for no reason, can I get any support for this?
It is in WEST Oregon, apparently the host cannot resolve and connect
10 Replies
a year ago
it doesn't return any errors, it simply doesn't connect to the API, when I access it it's normal and it only works again when I restart it
a year ago
where can I see this?
a year ago
I spoke to the programmer and we switched to v2 this morning
a year ago
Sorry I missed your message, let me know if the v2 runtime solves your issues or if you still experience them.
a year ago
It happened today after switching to V2, even changing the region it continued to be slow and falling as I explained, this has been happening since the general fall that happened a few days ago
a year ago
Hey there, I see that the API is in US East, was that also done as a troubleshooting measure?
a year ago
Since the rest of the services appear to be in US West, I think it'd be good to put it back in US West.
I'm also curious about the behavior when it's slow/failing. Is it trying to connect to another service and failing, or perhaps the downstream service is responding slowly? Do you intervene in any way, or does it self-resolve? It may be beneficial to put the rest of the services on the new proxy as well.
a year ago
I said new proxy, but the V2 runtime might be the way to go in this case too, as Brody mentioned. It depends on the details, but if you have an appetite for it - maybe enable both since they each provide huge benefits. I would do so for any services that the API connects to, particularly when it exhibits the degraded performance.