Opened 2 years ago

Closed 13 months ago

#23717 closed defect (wontfix)

Cannot create multiple temporary XMPP accounts in the same session

Reported by: huyvq Owned by:
Priority: Medium Milestone:
Component: Archived/Tor Messenger Version:
Severity: Normal Keywords:
Cc: sukhbir, arlolra, boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


TM version: 0.5.0b1 (based on Instantbird 1.6a1pre)

Steps to reproduce:

  • Create a temporary XMPP account -> succeeded
  • Create another temporary XMPP account. The Accounts window shows Error: without any details (please see the screenshot).

Debug Log shows:

LOG (@ prpl-jabber: XMPPParser.prototype._logReceivedData resource:///modules/xmpp-xml.jsm:349)
<iq xmlns="jabber:client" id="396b4d85-c241-7747-ad55-e1025d6a2ce9" type="error" from="">
<error xmlns="jabber:client" type="wait">
<not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>

Child Tickets

Attachments (1)

error.png (33.6 KB) - added by huyvq 2 years ago.

Download all attachments as: .zip

Change History (4)

Changed 2 years ago by huyvq

Attachment: error.png added

comment:1 Changed 2 years ago by sukhbir

Thanks for reporting!

I am guessing this is because is rate-limiting the new registrations from a given IP, which is what happens during one session.

I see two ways of fixing this:

  • throw up a better error message (which it should but since in this case it doesn't have much to go with other than "error", or maybe we are not handling it properly)
  • randomize the servers each time the user requests a temporary account (we can only do this with servers that don't use OCR during registration)

Suggestions welcome!

comment:2 Changed 2 years ago by huyvq

I think we should do both.

Can we let the user select the server he/she wants? ChatSecure provides a number of servers which don't require captcha during registration (

comment:3 Changed 13 months ago by traumschule

Resolution: wontfix
Status: newclosed

<+sukhe> hello. yes, I think it's fine to close the tickets. thanks for doing what we should done earlier :)

Note: See TracTickets for help on using tickets.