MongooseIM SSL connection via AWS ELB












0















I have MongooseIM server configured with docker-compose in an EC2 instance in AWS.



I intend to give access to some mobile clients with SSL through an ELB (AWS) on port 5222 (module ejabberd_c2s of mongooseim) in the following way:



(ignore de 5285 SSL config, it's for BOSH module and works fine)



ELB AWS



In the ejabberd_c2s module configuration I have the following:



  { 5222, ejabberd_c2s, [

%%
%% If TLS is compiled in and you installed a SSL
%% certificate, specify the full path to the
%% file and uncomment this line:
%%
{certfile, "priv/ssl/fake_server.pem"}, starttls,

%%{zlib, 10000},
%% https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS
%% {ciphers, "DEFAULT:!EXPORT:!LOW:!SSLv2"},
{access, c2s},
{shaper, c2s_shaper},
{max_stanza_size, 65536},
{protocol_options, ["no_sslv3"]}

]},


But customers can not connect, the only message I get on the server is this:



mongooseim_server_dev | 10:58:25.885 [info] (#Port<0.27608>) Accepted connection {{10,0,17,246},42571} -> {{172,18,0,2},5222}
mongooseim_server_dev | 10:58:25.885 [debug] Received XML on stream = "���yw���.ndEt�;�����fn�A>� n:�=5��</A
"ngooseim_server_dev | ��kj98����g@32ED�(#
mongooseim_server_dev | 10:58:25.885 [debug] Send XML on stream = <<"<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2B421BCD2D077161' from='localhost' version='1.0'>">>
mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"<stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>">>
mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"</stream:stream>">>


The Mongoose documentation does not offer me any solution and I do not see anyone with this error.



Any help or clue?










share|improve this question



























    0















    I have MongooseIM server configured with docker-compose in an EC2 instance in AWS.



    I intend to give access to some mobile clients with SSL through an ELB (AWS) on port 5222 (module ejabberd_c2s of mongooseim) in the following way:



    (ignore de 5285 SSL config, it's for BOSH module and works fine)



    ELB AWS



    In the ejabberd_c2s module configuration I have the following:



      { 5222, ejabberd_c2s, [

    %%
    %% If TLS is compiled in and you installed a SSL
    %% certificate, specify the full path to the
    %% file and uncomment this line:
    %%
    {certfile, "priv/ssl/fake_server.pem"}, starttls,

    %%{zlib, 10000},
    %% https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS
    %% {ciphers, "DEFAULT:!EXPORT:!LOW:!SSLv2"},
    {access, c2s},
    {shaper, c2s_shaper},
    {max_stanza_size, 65536},
    {protocol_options, ["no_sslv3"]}

    ]},


    But customers can not connect, the only message I get on the server is this:



    mongooseim_server_dev | 10:58:25.885 [info] (#Port<0.27608>) Accepted connection {{10,0,17,246},42571} -> {{172,18,0,2},5222}
    mongooseim_server_dev | 10:58:25.885 [debug] Received XML on stream = "���yw���.ndEt�;�����fn�A>� n:�=5��</A
    "ngooseim_server_dev | ��kj98����g@32ED�(#
    mongooseim_server_dev | 10:58:25.885 [debug] Send XML on stream = <<"<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2B421BCD2D077161' from='localhost' version='1.0'>">>
    mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"<stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>">>
    mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"</stream:stream>">>


    The Mongoose documentation does not offer me any solution and I do not see anyone with this error.



    Any help or clue?










    share|improve this question

























      0












      0








      0








      I have MongooseIM server configured with docker-compose in an EC2 instance in AWS.



      I intend to give access to some mobile clients with SSL through an ELB (AWS) on port 5222 (module ejabberd_c2s of mongooseim) in the following way:



      (ignore de 5285 SSL config, it's for BOSH module and works fine)



      ELB AWS



      In the ejabberd_c2s module configuration I have the following:



        { 5222, ejabberd_c2s, [

      %%
      %% If TLS is compiled in and you installed a SSL
      %% certificate, specify the full path to the
      %% file and uncomment this line:
      %%
      {certfile, "priv/ssl/fake_server.pem"}, starttls,

      %%{zlib, 10000},
      %% https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS
      %% {ciphers, "DEFAULT:!EXPORT:!LOW:!SSLv2"},
      {access, c2s},
      {shaper, c2s_shaper},
      {max_stanza_size, 65536},
      {protocol_options, ["no_sslv3"]}

      ]},


      But customers can not connect, the only message I get on the server is this:



      mongooseim_server_dev | 10:58:25.885 [info] (#Port<0.27608>) Accepted connection {{10,0,17,246},42571} -> {{172,18,0,2},5222}
      mongooseim_server_dev | 10:58:25.885 [debug] Received XML on stream = "���yw���.ndEt�;�����fn�A>� n:�=5��</A
      "ngooseim_server_dev | ��kj98����g@32ED�(#
      mongooseim_server_dev | 10:58:25.885 [debug] Send XML on stream = <<"<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2B421BCD2D077161' from='localhost' version='1.0'>">>
      mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"<stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>">>
      mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"</stream:stream>">>


      The Mongoose documentation does not offer me any solution and I do not see anyone with this error.



      Any help or clue?










      share|improve this question














      I have MongooseIM server configured with docker-compose in an EC2 instance in AWS.



      I intend to give access to some mobile clients with SSL through an ELB (AWS) on port 5222 (module ejabberd_c2s of mongooseim) in the following way:



      (ignore de 5285 SSL config, it's for BOSH module and works fine)



      ELB AWS



      In the ejabberd_c2s module configuration I have the following:



        { 5222, ejabberd_c2s, [

      %%
      %% If TLS is compiled in and you installed a SSL
      %% certificate, specify the full path to the
      %% file and uncomment this line:
      %%
      {certfile, "priv/ssl/fake_server.pem"}, starttls,

      %%{zlib, 10000},
      %% https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS
      %% {ciphers, "DEFAULT:!EXPORT:!LOW:!SSLv2"},
      {access, c2s},
      {shaper, c2s_shaper},
      {max_stanza_size, 65536},
      {protocol_options, ["no_sslv3"]}

      ]},


      But customers can not connect, the only message I get on the server is this:



      mongooseim_server_dev | 10:58:25.885 [info] (#Port<0.27608>) Accepted connection {{10,0,17,246},42571} -> {{172,18,0,2},5222}
      mongooseim_server_dev | 10:58:25.885 [debug] Received XML on stream = "���yw���.ndEt�;�����fn�A>� n:�=5��</A
      "ngooseim_server_dev | ��kj98����g@32ED�(#
      mongooseim_server_dev | 10:58:25.885 [debug] Send XML on stream = <<"<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2B421BCD2D077161' from='localhost' version='1.0'>">>
      mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"<stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>">>
      mongooseim_server_dev | 10:58:25.886 [debug] Send XML on stream = <<"</stream:stream>">>


      The Mongoose documentation does not offer me any solution and I do not see anyone with this error.



      Any help or clue?







      ssl amazon-web-services amazon-ec2 xmpp ejabberd






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 15 at 15:32









      user202890user202890

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394574%2fmongooseim-ssl-connection-via-aws-elb%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394574%2fmongooseim-ssl-connection-via-aws-elb%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How do I know what Microsoft account the skydrive app is syncing to?

          When does type information flow backwards in C++?

          Grease: Live!