What steps will reproduce the problem? 1. Establish session 2. Deactivate network 3. Reactivate network What is the expected output? Client should receive queued stanzas What do you see instead? mod_smacks resuming existing session... changed state from ready to error (ready) Traceback[c2s]: /usr/lib/prosody/util/stanza.lua:62: invalid attribute value: expected string, got number stack traceback: [C]: in function 'error' /usr/lib/prosody/util/stanza.lua:62: in function 'check_text' /usr/lib/prosody/util/stanza.lua:75: in function 'check_attr' /usr/lib/prosody/util/stanza.lua:87: in function 'stanza' /usr/lib/prosody/modules/mod_smacks.lua:406: in function </usr/lib/prosody/modules/mod_smacks.lua:365> (...tail calls...) /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75> (...tail calls...) /usr/lib/prosody/core/stanza_router.lua:142: in function 'core_process_stanza' /usr/lib/prosody/modules/mod_c2s.lua:276: in function 'func' /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125> What version of the product are you using? On what operating system? Prosody 0.11.1 Conversations 2.3.8

I suffer from this too

What version of mod_smacks / prosody-modules do you have?

• tags Component-Community Status-NeedInfo

I had the same issue and error after yum updating to prosody-0.11.0-1.el7.x86_64. Unsure of version of mod_smacks, it has no version string in the file, had labels: - 'Stage-Alpha' in the readme. Last copyright in the module was 2016-2017 Thilo Molitor. Doing a new hg clone of prosody-modules and replacing it with the updated one corrected the problem on my server.

Seems that I created a dup of this one? https://issues.prosody.im/1314