Signal-ios: Registration Error in 2.1.1 (Latest) on iOS 8.3
Im having trouble registering via the iOS app in Norway while trying to get my family to switch over to the service:
Registration Error
We couldn't reache the Signal server. Please try again.
Using wifi and 4G give the same results.
How can i assist?
Doing a:
curl master.whispersystems.org:31337
Gives me:
curl: (52) Empty reply from server
metrafonic
All 18 comments
Nmap gave me the following:
Starting Nmap 6.40 ( http://nmap.org ) at 2015-07-14 21:47 CEST
Nmap scan report for master.whispersystems.org (66.175.212.82)
Host is up (0.15s latency).
rDNS record for 66.175.212.82: us-e0.whispersystems.org
PORT STATE SERVICE
31337/tcp open Elite
Nmap done: 1 IP address (1 host up) scanned in 0.62 seconds
Hey @metrafonic,
We are currently working on a fix. Affects most users. Will give updates as time passes.
FredericJacobs
on 14 Jul 2015
I tried Signal a year or so ago and I couldn't register: the infamous "We couldn't reach the Signal server." error. I tried disabling wifi and using 3G or EDGE. Tried different phone numbers on different version of iOS, no luck. Today, a year or so later, I gave it a second try and... exactly the same issue.
People have been reporting this here, here, here, here, here and here and all conversations go dark after a while. No solution.
It does work on an Android phone on the same wifi network.
I want to love Signal, RedPhone, TextSecure or however you want to call it and still believe it's the gold standard of text messaging apps but after multiple phones and multiple versions I haven't been able to have a single decent conversation via Signal. So please, please... if you don't care just tell us you don't care so we don't loose hope every time you promise this will be fixed.
Now, it's open source, we don't pay you and you spend your time fixing bugs. I get that. If that's the problem please explain the bug so we can all help improve Signal. That's what open source is all about.
cimm
on 14 Jul 2015
// , My friend @jay-a-elliot, who cannot post this now, had a previously working Signal on version 2.0.
Version 2.1 breaks his app.
Since 2.0 was working, for him, can he revert back to it and still maintain compatibility with the overall Signal Network?
v6
on 15 Jul 2015
Same issues on iOS 8.4 with Signal 2.1.1 - when a call is initiated says "Client Failed!"
raduzl74
on 15 Jul 2015
With apologies, there's now an update in the app store which should resolve these issues.
moxie0
on 15 Jul 2015
@moxie0 Thank you! Care to explain why this happens from time to time? This seems like a recurring issue and it would be nice to understand what is happening. Thank you for your hard work!
cimm
on 15 Jul 2015
master branch still has this issue...not sure why the fix hasn't been pushed here.
ndrewh
on 16 Jul 2015
// , As far as I know, my friend has it working, but I think that the code for the application in the app store does not match the code in this repository.
v6
on 20 Jul 2015
Getting the same issue on iPhone 6s iOS 9.0.1 right now after upgrading from iPhone 6 which was working fine.
hubert3
on 26 Sep 2015
Same registration issue on iphone 6 IOS 9.1 with freshly downloaded signal app from store today.
franks42
on 10 Nov 2015
This issue persist on newest IOS on an iphone 6 with the newest version of the app.
bismuth
on 19 Nov 2015
@bismuth @franks42 : Can you retry? Does enabling "Background Fetch" in the settings change anything?
FredericJacobs
on 19 Nov 2015
Excellent! This fixed it without enabling Background Fetch, but it took me a few retries before the submitted verification code was accepted. I got two "server replied with status 0" (or something like that) messages before that. But thank you very much!
bismuth
on 19 Nov 2015
Hi,
I tried calling people on Signal but it does not work. Please fix the issue.
Radu
Please excuse brevity and typos. Sent from my iPhone.
On 20 Nov 2015, at 00:15, Jilles de Wit [email protected] wrote:
Excellent! This fixed it without enabling Background Fetch, but it took me a few retries before the submitted verification code was accepted. I got two "server replied with status 0" (or something like that) messages before that. But thank you very much!
—
Reply to this email directly or view it on GitHub.
raduzl74
on 17 Mar 2016
// , Radu, is this the same issue as described here: https://github.com/WhisperSystems/Signal-iOS/issues/852#issue-95005188
?
v6
on 22 Mar 2016
@v6 It was most likely this: #1115
2-4601
on 22 Mar 2016
Yes
Radu
Please excuse brevity and typos. Sent from my iPhone.
On 22 Mar 2016, at 03:48, 2-4601 [email protected] wrote:
@v6 It was most likely this: #1115
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
raduzl74
on 22 Mar 2016
Related issues
gabridome
·
4Comments
gonzalezb
·
5Comments
nanotechz9l
·
5Comments
maxbrandes
·
4Comments
loki187
·
3Comments
Most helpful comment
@v6 It was most likely this: #1115