Hi,
For around three weeks now, I’ve noticed that when the robot launches the browser to authenticate with the OpenCore cloud, the authentication process takes a very long time. Both before and after entering the credentials, the status remains Pending.
Has anyone else experienced this issue?
Yeah, I get spammed with monitor emails about servers being down or not responding after I scaled it down. Not sure what to do about it. I have 700+ users hammering on the servers, and I’m not making even 10% of the cost of running those servers.
I added one more server; let’s see if that helps a bit.
Thanks Allan.
What about non Free plans? Any dedicated servers for paid subscriptions? I see that dedicated server is for Cloud Advanced, right? Basic and Premium could have similar issues?
Just curious.
i think i just found the issue that made servers run out of memory and crash all the time.
need to monitor it close the rest of the day, but im 99,9% sure i found it …
All right then. Keep my fingers crossed 
[14:40:19.459][Warning] Message 5883f34d-8045-4f2b-bbf8-6d4bc50afdea (insertorupdateone) state failed timed out, retrying state:
[14:40:18.206][Warning] Message 05d35416-5acd-49cf-9165-d745bf57df20 (insertorupdateone) state loaded timed out, retrying state:
[14:40:18.203][Warning] Message 0bcc655f-54a7-40bd-a7e2-b8b27a4f509c (queuemessage) timed out, retrying
[14:40:13.264][Warning] Message d5d786bd-8629-417b-8d3d-847faaa4efff (queuemessage) timed out, retrying
[14:40:10.965][Warning] Message 9a27a2e6-0f67-4220-94fb-8bebe2be408f (insertorupdateone) state loaded timed out, retrying state:
[14:40:04.464][Warning] Message 5883f34d-8045-4f2b-bbf8-6d4bc50afdea (insertorupdateone) state failed timed out, retrying state:
[14:40:03.196][Warning] Message 05d35416-5acd-49cf-9165-d745bf57df20 (insertorupdateone) state loaded timed out, retrying state:
[16:56:02.190][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:55:47.188][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:55:32.186][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:55:17.184][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:55:02.182][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:54:47.179][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
[16:54:32.177][Warning] Message 2c81f180-fe0c-42f8-bd75-5b3c44110dfa (query) timed out, retrying
Hi, is this issue caused by the server too? It used to be working fine, but recently keep having these issues.
Yes, that is the same issue. The servers have been up for 4 hours now, so looking good so far.
ok, but I just able to login into opencore 10 minutes ago after 1 hour of trying to connect

[15:00:28.771][Warning] Message d1e03beb-4216-4a56-87a1-79fed573799d (query) timed out, retrying
[15:00:28.173][Warning] Message da65c662-ca12-441f-b30f-a30333de5e6e (query) timed out, retrying
[15:00:28.011][Warning] Message 89c2b670-18d9-43bb-b473-1f7cee5d47c2 (query) timed out, retrying
[15:00:17.981][Warning] Message 42e81935-2e49-4f46-ad77-4132527320d9 (query) timed out, retrying
[15:00:13.777][Warning] Message NOOP d1e03beb-4216-4a56-87a1-79fed573799d query
[15:00:13.776][Warning] Message d1e03beb-4216-4a56-87a1-79fed573799d (query) timed out, retrying
15:07:58.610][Error] RobotInstance.RobotInstance_WebSocketClient_OnOpen.userlogin: Gave up on 6c30f6d7-2c79-4a4c-b857-d44d0509cc1f signin
[15:07:58.610][Error] WebSocketClient.SendMessage: Not connected/signed in to OpenFlow
[15:07:58.608][Error] Gave up on 6c30f6d7-2c79-4a4c-b857-d44d0509cc1f signin not connected
[15:07:58.607][Warning] Message 6c30f6d7-2c79-4a4c-b857-d44d0509cc1f (signin) timed out, retrying
[15:07:43.599][Information] Connected to wss://app.openiap.io/
I think the issue still persists
No, its did resolved it. Server ran fine for 19 hours, so I am now working finding some cheaper servers that can match the memory usage they had the last 19 hours.
As long as i’m losing money i will keep testing ways to scale this down.