-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FQDN is not resolved again on reconnect #927
Comments
Hello everyone. Has there been any progress on this issue? |
Looks like you already figured out what the problem is. PR welcome - https://github.com/xmppjs/xmpp.js/tree/main/packages/reconnect |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@xmpp/client Version
0.9.2
Expected Behavior
When the connection is reset for some external reason, when trying to reconnect the FQDN should be resolved again in case it has changed.
Actual Behavior
In our case the FQDN (fcm-xmpp.googleapis.com) was always resolved to 108.177.15.188:5235 which failed every ~30 seconds with error:
Error: connect ECONNREFUSED 108.177.15.188:5235
Additional Information - What happened
Some days ago, google had an issue with some components, including firebase, which affected our XMPP connection to fcm-xmpp.googleapis.com (we use this FQDN in connect options). It seems that IP that the FQDN resolves to, changed. The XMPP client tried to reconnect and every ~30 seconds got this error message:
Error: connect ECONNREFUSED 108.177.15.188:5235
The issue was solved after we stopped the client and started it again. So it seems that on reconnect the XMPP client does not try to resolve again the FQDN.
The text was updated successfully, but these errors were encountered: