ejabberd - Comments for "How to save my configuration for Listened Ports module" https://www.ejabberd.im/node/4373 en configure it in ejabberd.cfg https://www.ejabberd.im/node/4373#comment-56789 <div class="quote-msg"> <div class="quote-author"><em>matiasMunoz988</em> wrote:</div> <p>I add the ejabberd_service into the server, but when I stop the Ejabberd Server and I restart, my ejabberd_service, is not there. So i have to configure my listening port, every time I start Ejabberd Server. I want to know if is there a way to save my ejabber_service, without configuring every time I log up..</p></div> <p>The configuration changes in the WebAdmin are not stored in ejabberd.cfg</p> <p>If you want to ensure a permanent configuration, configure it in ejabberd.cfg</p> <p>Related section:<br /> <noindex><a href="http://www.process-one.net/en/ejabberd/guide_en#basicconfig" title="http://www.process-one.net/en/ejabberd/guide_en#basicconfig" rel="nofollow" >http://www.process-one.net/en/ejabberd/guide_en#basicconfig</a></noindex></p> Tue, 02 Nov 2010 20:12:47 +0000 mfoss comment 56789 at https://www.ejabberd.im Hi badlop. Is not the https://www.ejabberd.im/node/4373#comment-56777 <p>Hi badlop. Is not the connection that closes. Maybe I didn't explain well. I add the ejabberd_service into the server, but when I stop the Ejabberd Server and I restart, my ejabberd_service, is not there. So i have to configure my listening port, every time I start Ejabberd Server. I want to know if is there a way to save my ejabber_service, without configuring every time I log up.</p> <p>I hope that my explanation be understood.</p> <p>Thanks.</p> Thu, 28 Oct 2010 13:20:55 +0000 matiasMunoz988 comment 56777 at https://www.ejabberd.im matiasMunoz988 wrote: I just https://www.ejabberd.im/node/4373#comment-56767 <div class="quote-msg"> <div class="quote-author"><em>matiasMunoz988</em> wrote:</div> <p>I just create an external component that connects to Ejabberd server</p> <p>the port that I created is non shown in the configuration</p></div> <p>Maybe your component has a bug, and it closes the connection with ejabberd.</p> <p>Or maybe your component sends a stanza to ejabberd considered offensive (e.g. with wrong XML syntax), and then ejabberd closes the connection.</p> <p>You can sniff the network traffic between your component and ejabberd to see who closes the connection. Maybe you discover why it gets closed.</p> Wed, 27 Oct 2010 21:51:03 +0000 mfoss comment 56767 at https://www.ejabberd.im