Verification Failed, Please Retry Later #6785
Comments
|
Repeated shutdown/ restart, with long waits, not helping to clear that the "verification failed" message every time I complete a capcha. I've lost count, but I've done maybe 6 or 7 of them. I now have a message to a group on hold, with the spinner going. Message that is failing to be sent: SentToday 8:23 PM That message is listed as "pending" for all members of the group. From my experience with something like this perhaps a year ago, I think it may be 24 hours before that times out. |
|
Sorry for this, @DiagonalArg; we are investigating. |
|
Now version 6.47.1 So I'm getting completely locked out now and blocked from posting on a couple of groups. This is a log subsequent to many solved capchas and multiple restarts over two days. Log.
Also, @jamiebuilds-signal had told me that if I blocked 6 people, that should help with (at least) the problem reported in [2] (see the OP, above). I have blocked those, to no effect, at least on this bug:
|
|
I can't get any verifications to go through, and I'm getting locked out of more groups. Log. A few minutes later, after a couple of more capchas, another log |
|
Reboot, followed by 5 completed capchas. No feedback from Signal save for the first capcha, for which I got the "Verification Failed, Please Retry Later." Then I gave up. Log I've got 3 groups now where messages are not just sitting with a spinner, but are completely failing. |
|
I'm getting messages failing silently. Signal really needs to be more noisy when, in a long thread, a message times out and doesn't end up being sent. Here is the log relevant to the details below: Here is a message from two days ago that was partially sent with one person for whom, after some great length of time, it failed. I've tried sending it again, and that person has now returned to "pending". They will stay there for some time, and then the message will probably fail again (?) There are also many people for whom I'm told that message was "sent to", though not "delivered to" (as with the bulk of them): SentFeb 15, 2024, 3:39 PM - (1708040375046)
A later message on that same group, that is showing two check marks, shows a number of people for whom it was "sent to" but not "delivered to". Oddly, that one person who failed the previous message is appearing in the "sent to" list differently from the others, though there is some icon missing so I can't interpret what might be going on here (notice the gap): SentToday 3:58 PM - (1708214295355)
I don't know if any of this has to do with that specific person, but they are in four of my groups. In a second one, I'm getting a "Send Failed" on a message that was "Not sent" to anyone on the group (ie. everyone is listed as "not sent"): SentYesterday 6:14 PM - (1708136048906)
An earlier one on that same group is getting a "Not Sent" for just that one person: SentFeb 15, 2024, 7:45 AM - (1708011957880)
On the other hand, a third group that they are in has a message that was successfully sent (two check marks, though there are many "Sent to" as opposed to "Delivered to"). There, this specific person is in the "Sent to" group, but again with this odd difference in the listing: SentToday 4:38 PM - (1708216738621)
Edit: Regarding that last message, there are still many in the "Sent to" column, but that one person has migrated to "Delivered to", though still with this odd difference - note, no time is listed!:
|
|
Now this is the group that was giving me so much grief in my report [2] (see the OP). I sent a message two days ago, and it came up as "Send failed" with everyone is listed as "Pending" (see the spinner in the image, still going) except one person, for which it was "Not Sent." Thing is, that person had left the group, so I'm not sure why they are still listed there at all: SentFeb 15, 2024, 3:49 PM - (1708040963719)
Edit: I tried deleting that message and resending (new log). It's 5 minutes now, and everyone is listed as Pending. There seems to be no action at all: SentToday 7:37 PM - (1708227440002)
I wonder how much is due to the capcha issue, because on shutdown and restart, I'm back to the request for capcha that is responded to with "Verification failed, please retry later." I'm dead in the water. I can't get through a /single/ capcha.
Edit: I deleted all these and resent from my phone, where capchas worked and were not excessive. |
|
Until yesterday, I did all posts on 4 problematic lists through my phone (desktop -> note to self -> forward to the list from phone). Yesterday and today I sent to one of those lists directly from the laptop, got one capcha, and was able to get through it unscathed. Alright, I just edited that message, it wanted another capcha, and then it fails. Log Reboot of the machine didn't help. Log. |
|
As far as I can tell, this problem appears to be fixed. (Version 7.0.0). Not sure if I should close, so I'll leave it open. Edit: Belay that - no, problem is still here. Log |
|
I posted this as a new bug. We are now at version 7.3.0. The problem remains, plus a new problem. At the very moment I try to submit the debug log, I get the following, plus a request that I complete another capcha. The debug log, when I try to attach here, says "File size too big: 25MG are allowed, 186MB were attempted to upload." Maybe you can give me a place to upload it?
|
|
This is still a problem, and in this case, I got capchas when posting to a group that /I created/! Now I can't post any more. Log. |
|
I just started getting this today right after creating a group and adding about 20 people to it (all of whom are friends). On the desktop app. |
|
Ya, it's beginning to spread. I've had trouble for months, but other people are starting to report the issue on the my threads. |
|
I've just gotten this issue when upgrading to 7.12.0. It's quite annyoing. The verification keeps failing and the recaptcha keeps popping up. Please for the sake of all our sanity ... roll back that commit. |
|
They say they are working on it. I hope others can report details. My FS has reported metadata errors, so I'm having to rebuild. I'll be a while. |
|
It just started for me. I was adding and messaging a few new contacts today. For the first two, everything was fine (I was asked once for Captcha), for the next two I am in infinite "Verification failed. Please retry later." loop. Artix GNU/Linux (rolling release), signal-desktop version 7.13.0. For now, I cannot message to new contacts, since I do not have any Android or iOS device in regular use (and thus also not with me on travel) and solely must rely on signal-desktop beeing not logged out. ("Signal is not for users who do not use an Android or iOS operating system".) |
|
@dreirund can you share debug logs when you are in a captcha loop? Thanks! |
|
Similar or same problem. Blocked from sending and receiving on the phone and one laptop. It starts when adding a new contact and asks for verification. The problem may result from using a double VPN connection that captchas tend to have to run two or three times to validate the connection. As a future update, perhaps: a) verification is tied to the pin and not to a captcha and/or b) there is a way in settings to retrigger the account verification that had previously failed. It never offers an on demand chance to validate later on mine. It just blocks all new messages (circles forever when trying to send). Version 7.17 (171) on an iPhone 11 |
|
No double VPN on my end. Just a single. |
|
@dreirund can you share debug logs when you are in a captcha loop?
I just wanted now, but now (after a few days) it worked even without
any captcha.
So I cannot reproduce for now.
I did not update my system in the meantime, nor did I log out or log in
at all.
(Can it be that Signal has some block that allows only to add a few new
contacts per day or so, and does not report this cleanly back to the
user but resulting in a CAPTCHA-Loop?)
|
|
@NicholasTaylor Thanks for providing all the details in your bug report. You can reach out to support@signal.org so folks here won't get access to your logs. |
|
Mine, I had to reinstall Signal on the phone. There was no future opportunity to rectify the block and get the app reactivated. And that's a problem. If you can't get it to run because of use of a VPN, then turn off the VPN and try, that won't solve it. You've lost any chance to use the app. that also meant losing all chats. So it seems like the PIN entry would be a better way to do this. |
|
If you can't get it to run because of use of a VPN,
Signal should not block any VPN usage.
For some use scenarios VPN (in combination with shadowsocks even) is
vital to get "out to the world" at all, or to circumvent possible law
enforcement.
If VPN "kills" Signal usage, than that is a major issue.
|
|
Ubuntu 22.04, Signal Desktop 7.15.0. (I was able to get my system up and going again, after a hardware issue.) After avoiding it for some time, "Verification failed, please retry later", and repeated requests that I do another capcha: Edit: Ok, I'm starting to get messages paused on Android. Message info is not giving me a message ID. It just says, "Sent - Via Pending..." Here's the android log: |
|
Messages are piling up again. Signal Desktop 7.16.0. Signal Android 7.10.3. |
|
I hope developers will bypass this problem altogether by requiring the pin to authenticate the account to prove that the request is not spam. So simple. PIN verification is done intermittently anyway to prove it's the owners' account, so why wouldn't this work for verifying that this is not spam? Anyone reading this, can you knock down this idea as to why it wouldn't work? |
|
@Curnon , this is about blocking bots. |
|
If a PIN can't be used to assume not a bot, then try changing over to the awesome Cloudflare Turnstile in beta! |
|
changing over to the awesome Cloudflare Turnstile in beta!
Wouldn't that give Cloudflare a lot of telemetry and thus is
anti-privacy?
|
|
"Stronger privacy Turnstile always preserves the privacy of web visitors on your site - without sacrificing effectiveness. Unlike other CAPTCHA options, we never harvest data for ad retargeting." https://www.cloudflare.com/products/turnstile/ Also, on GDPR compliance, it states: "Cloudflare is a privacy-first company. As such, the General Data Protection Regulation (“GDPR”) represents many steps we were already taking. We do not sell personal data we process, or use it for any purpose other than delivering our services. In addition, we let people access, correct, and delete their personal information, and give our customers control over the information passing through our network." https://www.cloudflare.com/trust-hub/gdpr/ Getting a captcha solution that may eliminate the ridiculous (yes, that's how it's spelled), failing captcha problem. |
|
"Stronger privacy
Turnstile always preserves the privacy of web visitors on your site -
without sacrificing effectiveness. Unlike other CAPTCHA options, we
never harvest data for ad retargeting."
https://www.cloudflare.com/products/turnstile/
That is what they say.
I learned to not trust self-statements of commercial players.
|
|
@DiagonalArg Pretty harsh. A potential workaround counts as a bugfix through a potential alternative route that negates the bug any day of the week. |
|
Ubuntu 22.04, Desktop Signal 7.16.0. "Verification Failed, Please Retry Later" is becoming common again. |
I'm still experiencing this. Debug log - created immediately after experiencing the issue. Version: MacOS Desktop 7.18.0 I use a VPN, but I tried to launch the app with the VPN off and still got the problem. This seems to be a fairly widespread issue: #6038, #6803, #6455, #6892, #6474 |
|
Following up on this. I was able to solve the infinite loop by doing the following:
It didn't go into an infinite loop of captchas in that case. I have yet to see how long this will last or what will happen after I turn the VPN back on. I use PortonVPN. |
|
I was able to solve the infinite by doing the following:
1. Closing Signal
2. Turning off my VPN (and leaving it off for a couple minutes just
in case) 3. Turning signal on
4. Completing the verification CAPTCHA
Signal targets privacy aware users.
So it _should not_ have inferior user experience if someone uses VPN.
|
|
Is this being investigated/worked on? Hard to tell from the limited contributor responses in this thread. Is there more information needed? I use ProtonVPN on all my devices and got into the captcha loop when adding a new contact on desktop. The contact added me back and we can communicate from my phone, but I am unable to send them any messages from desktop. My VPN is always on and I'm not going to turn it off to work around this bug (would rather switch to SimpleX than turn off my VPN). I have changed VPN servers and VPN countries but nothing fixes the problem. Where can I find Signal logs on Windows desktop? |
|
I was having the same trouble today—did the verification like 10 times with no success. After reading about "Cloudflare" comment above, I tried changing the DNS provider in Chrome's "Security" settings, but it didn't solve the problem. I finally fixed it by switching my default browser to Brave. Just 1x verification and it already worked! I think something in Chrome was blocking the verification info from reaching the Signal app. So, if you're having the same issue, try switching your default browser to something other than Chrome. |
|
Neither brave nor firefox worked for me for verification. Both in private/incognito windows (which is where I do all of my browsing). The captcha allegedly passed in all cases, though I have learned that sometimes when captchas say they pass to the user they are actually lying and they just are shadow blocking you. Maybe that is what is happening here? |
When you had this problem, was Signal not being re-opened (from Chrome)? I had an issue like that in the past, but I think it was a different issue. It wasn't an infinite loop, it was just an incomplete verification. We might need to open a separate issue for that one. (I haven't had that issue in a couple of months so don't have much to say about it). Only thing that has worked for me is turning off my VPN. |
and others
Using a supported version?
Overall summary
Ubuntu 22.04
Signal 6.46.0
I'm reporting extensive bugs in the capcha system, but things are not getting better. To the contrary. Recent, previous bug reports 1, 2, 3 - I believe related, 4 - on iphone.
As you see with [1], I was having trouble getting Signal to respond properly once I completed a capcha. I was able to get around that by restarting, sometimes more than once. Now, I am filing out a capcha, on each return to Signal I"m getting the message, "Verification failed, Please retry later." Then I restart, and try again, with the same message. I've done that now five times, so at this point I'm completely stuck. None of this had anything to do with the groups that have been causing me grief in the past, forcing multiple capchas on me in a row. I had just forwarded a message to 2 groups from a 3rd, all of which have behaved well in the past.
I produced this log.
Edit: I did two capchas in a row, without a restart in between. The second time I returned to signal, it was silent, no message, but the "Verify to continue messaging" window didn't go away.
New log.
Steps to reproduce
Above
Expected result
Above
Actual result
Above
Screenshots
No response
Signal version
6.46.0
Operating system
Ubuntu 22.04
Version of Signal on your phone
6.59.0.23
Link to debug log
No response
The text was updated successfully, but these errors were encountered: