Generic Network Error during Leo submission

I am having the same issue as

Yet I have two accounts and barely use the second…they both get the same error…instead of disabling an account in the middle of the month, why not just increase the payment?

Also similar to

Also similar to

There was a conversation about it last year

I have ended my second subscription because it is getting me no responses due to this error.

Same for me! It appeared in the last 1-2 days, and I constantly getting the

There was a network issue connecting to Leo. Check your connection and try again.

2 Likes

Yes! Exactly one and half days ago for me…and the problem continues today…

Can we consider ourselves actually intelligent when we pay $15 for an AI that takes frequent long coffee breaks?

1 Like

It seems to be back online to me. At least my requests in the last 2 hours got through

1 Like

Yes. Everything has been working great for the past few days! Thanks to all the unseen hands!

strangely this also happens for non premium users if you add your BYOM Anthropic API Endpoint, but in that case it just never works not even sometimes

Another Premium user has unexpectedly encountered the same connection error across all models. Repeatedly tapping “refresh” eventually allows Leo to connect, though this is not a permanent solution.

1 Like

This happens all day today:
Screenshot_2024-09-1i5

Still a big issue. I’d say in the last day I’ve seen more failures than replies in the last couple of days (since retrying, most often doesn’t work the first time). This is on the premium model.

Today this was happening again all the time.

2 Likes

I’m having the same issue on a paid Leo Premium plan…it’s very frustrating. I have to constantly hit “Retry” over and over until it works. And then a few minutes later the same issue happens again.

1 Like

Is there any type of official support for the paid Leo product? This network issue is still occurring.

1 Like

If this has been an ongoing experience with this issue for over a year. Would it be best for us to cancel our subscriptions? It seems like the model is based on a limited number of tokens, and we are just taking chances with each response, hoping it won’t be our last. I wish I had been more aware of this before using up my subscription on the first day. Or if there are still availability issues with the number of clients accessing the LLM, can we get an estimate of when we will be able to access it? I spent an hour troubleshooting my internet, only to find out that the error message was false and the issue was with the subscription. I have read the other reports, but they never specify the solution. Nevertheless, the reports are closed. It’s starting to sound like a cash-grab scheme.

1 Like

This happens again all day today. It fails 5 times in a row and then randomly works on the sixth, or on the tenth. It’s like dice roll almost every time with a low probability of success. It’s becoming very annoying The issue does come and go quite often. Can you at least make the error message more meaningful? Am I hitting some limit from my IP? (I’m using VPN) Am I timing out? (I doubt it, the error often pops up in less than 1 second) Can you provide some page with public statistics about the fail rates of Leo? Can you make it automatically retry and show us a message about the system being too busy while it retries so that I don’t have to keep pressing retry manually?

This is still ongoing and version 1.73.89 broke things even worse for me. Now clicking the Retry button does nothing at all. See my message here: Brave keeps resetting my Leo Premium model to Mixtral - #7 by Tritonio

EDIT: I reverted to 1.71.123 and now the retry button for Leo works again. I’ll try to go forward gain to 1.73.89 and check if it breaks again or if it was one time thing. I’ll edit this message again.

EDIT2: I installed 1.73.89 again and yes the button is definitely broken. Also notice how quickly I can do these tests, because Leo network-fails practically every time I try to use the improve text functionality on a page and I need to click retry a bunch of times to get a reply. :weary:

Omg… now the retry button seems broken on Android version 1.73.89 too.

This is a showstopper for me. I get network errors on the regular and now they completely kill the discussion as there’s no way to overcome them. And I cannot easily downgrade on my Android like I’ve done on Linux.

EDIT because I cannot post a third reply in a row:

This is issue have been almost constantly present since August. It seems to be lmost 100% guaranteed when I open start a discussion as a result of one of the Improve Text functions but it happens in almost every conversation I have with Leo, very often at the beginning, but sometimes later in the conversation too.

I did some debugging again using the net-exporter functionality of brave and I found that the actual error is: “Invalid or missing SKU credential” It happened three times in a row after simply saying “Hi” to Sonnet. And the fourth time it just worked.

I just tried to reset my SKU state as @Evan123 suggested above. I’ll see how it goes. I’ll do so on my other devices (I have Leo on desktop, laptop and an android phone, so three devices in total, and I used to have it on one more laptop but not currently). Am I hitting some device limit by any chance? Is that what’s causing all my issues? In the past it used to be the case that I couldn’t even login to more than one device, it would keep forcing me to log in again and again as I switched between laptop/desktop etc. Now it never forces me but perhaps there re still issues with multiple devices?

EDIT2: I noticed tht even after resetting the state, sometimes if I highlight text in a textfield and right click on it and use the Leo->Improve functionality, it will fail with network error but in reality the error from the server is starting like so:

“error”:{“type”:“40001”,“message”:"[{‘type’: ‘literal_error’, ‘loc’: (‘body’, ‘events’, 0, ‘ContextURLEvent’, ‘type’), ‘msg’: "Input should be Tag.contextURL:‘contextURL’", ‘input’: ‘userText’, ‘ctx’: {‘expected’: "<Tag.contextURL: ‘contextURL’>"}, ‘url’: ‘https://errors.pydantic.dev/2.7/v/literal_error’}, {'typ[stopping here because it’s huge]