Cloudron Forum

@girish said in Error 500 in DocuSeal After Update to Version 1.5.0:

@qwerti said in Error 500 in DocuSeal After Update to Version 1.5.0:

The current version is 7.5.2; perhaps we should consider updating it.

This is most likely the root cause. redis has changed in versions a lot since. Specifically, the newer versions of redis added acl support and also do not support empty redis usernames. I have set the minBoxVersion for docuseal now so it doesn't get installed.

Sorry for the late response. We just installed the latest version yesterday, and now everything is working again. Thank you very much for your help.

The current version is 7.5.2; perhaps we should consider updating it.

Yes, we have already restarted the app, but unfortunately, this did not make any difference. Installing a new container works, but the problem persists in the freshly installed system as well.
We suspect it might be something specific to our Cloudron setup since none of you seem to be experiencing these issues.

@nebulon said in Error 500 in DocuSeal After Update to Version 1.5.0:

Just updated my personal instance and that seems fine. Also a fresh installation show now error in the features I've tried.

Can you maybe explain in more detail how to reproduce this? Also is the redis container for that app working? You can check in the services view.

Thank you for the quick response. Unfortunately, we are not sure why this issue is consistently reproducible on our end. The Redis service is running perfectly.

Hi,

After updating DocuSeal to container-version 1.5.0, we are encountering a 500 error on almost every action within the application. Below is the relevant log entry:

Aug 05 13:24:22 /home/cloudron/rbenv/versions/3.3.3/lib/ruby/gems/3.3.0/gems/redis-client-0.22.0/lib/redis_client/connection_mixin.rb:71:in `call_pipelined': WRONGPASS invalid username-password pair or user is disabled. (RedisClient::AuthenticationError)

This issue persists even when we completely reinstall the container. It seems related to the Redis authentication.

Has anyone else experienced this issue or have any suggestions for resolving it?

Thanks in advance for your help!

Best regards