Skip to content

[Bug]: No Client Access after 1.4.14 Upgrade #210

@svandive

Description

@svandive

Description

Had a fully functional Bulwark --> Stalwart (v0.15.5) setup. I updated the Bulwark container to 1.4.14, and now Users can no longer login.

Accessing the Bulwark Login screen works fine. Entering credentials fails with the Error:
An unexpected error occurred. If this persists, contact your administrator.

No information or detail about the failed login is listed in the Bulwark logs (set to DEBUG).

Stalwart is configured for basic password authentication. Access from other JMAP clients works fine.

Admin Page login works fine, but of course uses a completely different methodology to Client login.

Without logs to identify an issue, I'm not sure where to go from here.

Steps to Reproduce

Upgraded operational Stalwart 0.15.5 + Bulwark implementation to 1.4.14. No other changes or updates.

Expected Behavior

If solution was accessible prior to upgrade the expectation is of course that you can login post upgrade.

Actual Behavior

Error on Login Screen: An unexpected error occurred. If this persists, contact your administrator.

I have to ask, are there expected errors???

Bulwark Version

1.4.14

Stalwart Mail Server Version

0.15.5

Browser

Safari

Operating System

macOS

Screenshots / Screen Recording

Image

Relevant Logs or Error Output

I wish...

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions