guardianproject / ChatSecureAndroid

This project has ended, but ChatSecure iOS continues. For Android, please use Conversations or Zom instead
https://chatsecure.org/blog/chatsecure-conversations-zom/
Apache License 2.0
1.07k stars 522 forks source link

Connecting to Ejabberd Service using Required TLS #723

Open DouglasDigital opened 8 years ago

DouglasDigital commented 8 years ago

Hello

I have an Ejabberd XMPP server running at a.ioneh.com.

I installed a Startssl Cert for the server.

I chose to REQUIRE TLS for all connections.

I have tried three other clients, they all connect fine. Chat Secure hangs on the "Singing in..."

Suggestions?

n8fr8 commented 8 years ago

Is the server open registration? Or can we get a test account?

Are you using the Tor option? Is there a SRV record?

Also are you on Marshmallow?

On Sat, Nov 14, 2015, at 10:49 AM, DouglasDigital wrote:

Hello

I have an Ejabberd XMPP server running at a.ioneh.com.

I installed a Startssl Cert for the server.

I chose to REQUIRE TLS for all connections.

I have tried three other clients, they all connect fine. Chat Secure hangs on the "Singing in..."

Suggestions?


Reply to this email directly or view it on GitHub: https://github.com/guardianproject/ChatSecureAndroid/issues/723

DouglasDigital commented 8 years ago

Sorry for the late reply.

The Server is now open for registration ioneh.com it's not ready for what I'm doing with it, but I need it working smoothly with chatsecure first.

Yes there are working srv records. I have absolutely no issues connecting with xabber but I'm not happy with it's security. I'm guessing this is me missing a cypher or something similar? Also I' running on a VM which letsencrypt wouldn't install ssl onto.

My results from the last scan are also up on https://xmpp.net/result.php?domain=ioneh.com&type=client

Thanks!

Not on marshmallow, 5.5.1 I believe or 5.1.1 (dyslexia and server management are an annoying combo)

toralf commented 8 years ago

Observed a similar problem here, ejabberd settings are:: s2s_use_starttls: required_trusted Eventually I could managed the login (and after the first login it now works flawlessly) - but I dunno, why it failed before few times in a row.

tomgagdotnet commented 8 years ago

I have a similar problem, but it didn't solve so far for me:

https://github.com/guardianproject/ChatSecureAndroid/issues/746