From 12:00 (CET) we started receiving a lot of following error: “An existing connection was forcibly closed by the remote host” in connection with Victron MQTT servers.
Any idea why? Were any changes on Victron side?
From 12:00 (CET) we started receiving a lot of following error: “An existing connection was forcibly closed by the remote host” in connection with Victron MQTT servers.
Any idea why? Were any changes on Victron side?
Any chance you have exceeded the rate limit and are now restricted?
Not this error. This error means connection has been establish but suddenly was closed by mqtt server in the middle of conversation. I think rather mqtt servers should be restarted.
14:00 - the same…
Not all, but about 50% connections.
And you definitely don’t fall into this (recently updated) category:
Most endpoints are by default rate limited with a rolling window of max 200 requests, where every 0.33 seconds a request gets removed from the rolling window. (so on average maximum of 3 requests per second won’t get rate limited). There are different types of ratelimiting in VRM. If you receive a 429 with a JSON response, you can check the Retry-After response header to check the amount of seconds you have to wait until retrying.
You are talking about WebServices of VRM. I’m taking about connection to Victron MQTT servers.
This is not the same.
MQTT requests are also subject to limits, this was implemented not that long ago to reduce loading.
Today at 12:00? Up to 12:00 everything worked well. I don’t change anything on my site.
Probably unrelated then, but was worth mentioning.
I have posted a note internally.
Correcting a previous post. There is nothing obviously wrong with the farm, it looks fine. Feedback is this is probably rate limiting but we will need some site ID’s to check.
But now I receive other errors: Error while authenticating. Connection closed.
But normally I can connect with MQTT and get SOC.
Mqtt service is now very unstable.
Mqtt is not WebService. It is taking server to server, not just ask-and-answer.
I notice your server disconnect mqtt conversation during connection and later during conversation.
I connect to mqtt, start querying and suddenly in the middle of conversation I receive error: The MQTT client is disconnected. Why? Because I break some limits? In the middle of conversation?
What are the current limits? How can I work according to your requirements? Is there any place I can find something about it?
The community cannot answer these questions. We’re trying to help. Ultimately you are running a commercial offering off a system designed for moderate end-user use. As per messages, there is no obvious issue and we can only get some clarity tomorrow.
Suddenly from 22:00 CET everything returned to normal. Thank you.
@Piotr the issue is understood, team is looking into preventing it in future.