latest package broke slack integration

[psifertex 0]

The: "Update to base image version 4" update broke my slack integration. I rolled back via a backup and it's now working correctly, but that seems particularly odd given that it didn't contain an update to chatwoot itself.

I thought at first it might be related to: https://github.com/chatwoot/chatwoot/issues/6377

But that looks like it was resolved before the latest chatwoot release so not sure what might be causing it. Happy to provide any extra debug logs if that would be helpful.

[girish]

@psifertex-0 That might actually be the issue. The new base image is Ubuntu 22.04 based (previous one was Ubuntu 20.04 based). Upstream fixed their deployment by rolling back their heroku stack.

[girish]

This should hopefully work now.

before:

# SLACK_API_TOKEN=whatever slack chat postMessage '--text=helloworld' --channel=@girish
error: SSL_CTX_load_verify_file: system lib

after:

# SLACK_API_TOKEN=whatever slack chat postMessage '--text=helloworld' --channel=@girish
error: invalid_auth

@psifertex-0 can you try with the latest package (1.16.0-1) ?

[psifertex 0]

@girish When I go to update from 1.15.0 it only shows me 1.15.1 as the next update. Am I required to first go to that broken version before 1.16 will show up? I clicked "check for updates" but it didn't appear to change anything.

I'll try to update to 1.51.1 and see if I can then update to 1.16.

Yeah, that let me update to 1.16. Is that expected behavior?

Yup, that fixed the bug, thanks! I'll probably still disable auto-updates going forward but I appreciate the quick turn on the fix.

[girish]

@psifertex-0 yes, correct, we always do rolling releases. One cannot jump releases.

[psifertex]

FYI -- This appears to have happened again with the latest 1.18 update. Specifically, Slack integration is silently failing/not available.

[psifertex]

Nevermind -- looks like just a stale session. New one worked fine!