> What steps will reproduce the problem? 1. start an xmpp session with a mobile client 2. put the client application to background (socket will be closed by OS) 3. bring application back to foreground (SM resume will be sent) > What is the expected output? No error. > What do you see instead? With debug enabled: https://h.tenak.net/dejisitugo.txt > What version of the product are you using? On what operating system? Debian stretch package for prosody-0.11 > Please provide any additional information below. The lines from logs before the traceback: https://prosody.im/pastebin/b877542e-6cd3-4113-b08e-226cd9739283 Thanks!

Seems that we have another similar traceback, but this hits a bit harder https://h.tenak.net/esisubikev.txt

In this traceback there are a few more lines, in case they're useful https://h.tenak.net/ujacaveqex.log

I'm now seeing this even with a non-mobile client, just a web application with a stanza.io client connected. All of this using a proxied websocket connection with nginx. The nginx config is as follows: ``` location /xmpp-websocket { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Forwarded-Https $https; proxy_read_timeout 60s; proxy_pass http://xmpp-server:5280/xmpp-websocket; }```

This was a configuration issue. Better handling implemented in https://hg.prosody.im/prosody-modules/rev/3d4eefdd950a

• owner MattJ
• tags Status-Fixed

• tags Component-Community