Server returned error: remote-server-timeout (#587)

Server returned error: remote-server-timeout (#587)

Open

Activities

	Unknown opened 2 years ago my server is prosody. registration is enabled `allow_registration = true` user can login only after prosodyctl adduser
	Unknown commented 2 years ago tested adium doesn't have such issue it looks only with beagle-im
	Unknown commented 2 years ago Please provide necessary details from the template for reporting bugs, such as: version of BeagleIM version of Prosody Additional information, this error usually means that BeagleIM did not receive response from the server.
	Unknown commented 2 years ago beagle im Version 5.3.1 (162) prosody with `allow_registration = true modules_enabled register` Prosody 0.11.13 # Prosody directories Data directory: /var/lib/prosody Config directory: /etc/prosody Source directory: /usr/lib/prosody Plugin directories: /usr/local/lib/prosody/modules - not a directory! /usr/lib/prosody/modules/ # Lua environment Lua version: Lua 5.2 Lua module search paths: /usr/lib/prosody/?.lua /usr/local/share/lua/5.2/?.lua /usr/local/share/lua/5.2/?/init.lua /usr/local/lib/lua/5.2/?.lua /usr/local/lib/lua/5.2/?/init.lua /usr/share/lua/5.2/?.lua /usr/share/lua/5.2/?/init.lua Lua C module search paths: /usr/lib/prosody/?.so /usr/local/lib/lua/5.2/?.so /usr/lib/x86_64-linux-gnu/lua/5.2/?.so /usr/lib/lua/5.2/?.so /usr/local/lib/lua/5.2/loadall.so LuaRocks: Not installed # Network Backend: select # Lua module versions lfs: LuaFileSystem 1.8.0 libevent: 2.1.12-stable luaevent: 0.4.6 lxp: LuaExpat 1.3.0 socket: LuaSocket 3.0-rc1 ssl: 1.0.2
	Unknown commented 2 years ago I am encountering the same problem. Here is some data from the debug logs on the server, if it is helpful: Jan 19 02:03:59 c2s80bbd3ac0 info Client connected Jan 19 02:03:59 c2s80bbd3ac0 debug Client sent opening <stream:stream> to mydomain.tld Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: <?xml version='1.0'?> Jan 19 02:03:59 c2s80bbd3ac0 debug Sent reply <stream:stream> to client Jan 19 02:03:59 c2s80bbd3ac0 debug Not offering authentication on insecure connection Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: <stream:features> Jan 19 02:03:59 c2s80bbd3ac0 debug Received[c2s_unauthed]: <starttls xml:lang='en' xmlns='urn:ietf:params:xml:ns:xmpp-tls'> Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'> Jan 19 02:03:59 c2s80bbd3ac0 debug TLS negotiation started for c2s_unauthed... Jan 19 02:03:59 c2s80bbd3ac0 debug Invalid opening stream header ({jabber:client}iq) Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: <?xml version='1.0'?> Jan 19 02:03:59 c2s80bbd3ac0 debug Disconnecting client, <stream:error> is: <stream:error><invalid-namespace xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error> Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: <stream:error> Jan 19 02:03:59 c2s80bbd3ac0 debug Sending[c2s_unauthed]: </stream:stream> Jan 19 02:03:59 c2s80bbd3ac0 debug c2s stream for 73.X.X.X closed: invalid-namespace Jan 19 02:03:59 c2s80bbd3ac0 debug Destroying session for (unknown) ((unknown)@mydomain.tld): invalid-namespace Jan 19 02:03:59 c2s80bbd3ac0 debug Discarding data received from resting session: <query xml:lang='en' xmlns='jabber:iq:register'/> Jan 19 02:03:59 c2s80bbd3ac0 debug Discarding data received from resting session: table: 0x80bc1a080 Jan 19 02:03:59 c2s80bbd3ac0 info Client disconnected: connection closed Jan 19 02:03:59 c2s80bbd3ac0 debug Destroying session for (unknown) ((unknown)@(unknown))

Issue Votes (0)

Watchers (0)

Reference

tigase/_clients/beagle-im#587

Please wait...

Page is in error, reload to recover