Hi I am developing an XMPP chat application. The chat is working properly and I have a problem with Stream Management. I have added the following settings in my server
In this I enabled stream_management. But I am not able to get sm xmlns='urn:xmpp:sm:3’ while connecting. Is there any other setting required for this? Please help me to solve this issues.
I expect that you are using an old ejabberd version (like for example ejabberd 2.1.11. ejabberd 2.1.11 does not support stream management, so what you see is the expected behaviour.
If you want to use stream management, you need at least ejabberd 14.07, but preferably the most recent version is better.
Related
I have made a plugin for Confluence v7.13.7. It is working absolutely fine in the Confluence server which is set up locally on my machine. But, when I tried installing the plugin in the client’s instance who is also using the same Confluence version 7.13.7 but using the data center version, the plugin got installed but not giving any result upon hitting the API endpoint.
Is this possible that a plugin can work in a server edition but cannot work in the data center? If this can happen, what are the possible reasons for this?
Please refer to https://developer.atlassian.com/platform/marketplace/developing-apps-for-atlassian-data-center-products/ to learn the difference of apps for DC. Most features will work the same it DC as in Server, but as it uses several nodes, you have to think how to transfer the same objects between them
For one of my application, I have implemented Web socket using socket.io and hosted in IIS. Currently socket connection helping to provide two way connection between client (React) and server (node.js).
As I mentioned, I have hosted my application in IIS. I have few doubts regarding Turn Windows features on or off -> Internet Information services -> World wide Web Services -> Application Development Features -> WebSocket Protocol. I have tested my application without enabling this feature, its working fine, but I would like to confirm below stuffs.
WebSocket Protocol
Do I really need to enable WebSocket protocol feature to make websocket work in my application? If so, how now it is working fine without enabling (I haven't do performance and stress testing, I may face issue on this).
What if I not enabling this feature? in short what is the actual use of this feature?
It would be helpful if anyone answer the above questions. Thanks in advance.
WebSocket as part of the HTTP stack requires a bunch of things to be ready on Windows (across multiple components), so hope this answer helps a little.
HTTP.sys, a driver deep down in Windows OS, is upgraded to support the necessary packet communication required by the protocol.
The IIS WebSocket module, an IIS extension which many other Microsoft frameworks (like SignalR) depend on.
So WebSocket support is by default on in HTTP.sys, and you don't need the IIS module if your framework (socket.io) has no dependency there.
Note that the "Summary" section provides several useful links,
https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-websocket-protocol-support#summary
and the same article also reveals that IIS WebSocket module has
conflicts with socket.io.
I was searching for solution to use xmpp library on flutter to connect with ejabberd server for chatting app. Anyone's suggestion will be very help for me.
XMPP connection made with flutter by using the xmpp_stone library. My Github repository is here. The main problem is, it connects without tls connection. In your ejabberd configuration yaml file line starttls: true, starttls_required: true should be commented.
If you have a better solution please suggest me. Thanks in advance!!!
I founded one way to connecting ejabberd server flutter given Strophe library enter link description here Strophe.js is an XMPP library for JavaScript. Its primary purpose is to enable web-based, real-time XMPP applications that run in any browser.
We are working on a project that uses Open fire(Xmpp) protocol. I have to capture that traffic(xmpp). suggest me tool and process.?
does wireshark work for xmpp traffic.?
Another suggestion only relevant if you happen to be using Smack:
If you are just trying to debug the traffic for a particular client while developing it and you happen to be using Smack as your client side library (just a guess since we are talking about openfire), then you can also make use of the Smack debug console. Adding the Java system property -Dsmack.debugEnabled=true will cause a debug console window to open each time an XMPP connection is established. IT shows traffic in/out and other useful information.
Yes, Wireshark works for XMPP traffic, as long as it is unencrypted.
If the connection is encrypted, you may be able to decrypt it by following the instructions at https://wiki.wireshark.org/SSL .
For monitors conversations and statistics of the openfire server,you can use Monitoring Service plugin in openfire.
For install
Go to server web amdin panel
Go to plugin menu
click on available plugin
find and install Monitoring Service plugin.
I am currently using the ConverseJS library in order to connect to the XMPP server and it is working pitch perfect. The one problem I am facing is that I want the chat history and in XMPP there is a function to fetch the message. I am using the Openfire Server and using the Monitoring plugin's latest version as well.
When I open any chat window then the spinner runs and then no old messages are shown. In the console log it gives the following error:
iq type="error" id="334" to="user1#mydomain.com/458">
<error type="cancel" code="501">
<feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
</error>
</iq>
So can anyone tell me any possible solution regarding this problem.
Finally solved it. In Openfire, there is setting where you can allow to fetch the chat history. Its value was 0 and it was stopping from fetching the history. But as I entered 7, then i started sending the history.
Hope this will help others as well.
Please make sure install plugin Monitoring Service and then server restart.
also make sure open fire version 3.10.* for Monitoring Service 4.6 .
follow this link https://community.igniterealtime.org/thread/57111, it may be work for you.
it is work for me.