#malformed gitAuth breaks instance
1 messages · Page 1 of 1 (latest)
Hey There,
We've registered your query, and our team will get back to you soon.
Regards,
Pranav
Could you provide some additional context here? I can't see any other threads
from you related to this.
i'd like to point to https://community.appsmith.com/t/malformed-gitauth-breaks-instance/2222, but
this is running a self-hosted appsmith in kubernetes; i can provide helm values if helpful
on minor version upgrade, appsmith became essentially unusable with a toast indicating "Internal server error while processing request" and producing the attached logs
there is an application imported from git(lab), which appears to have bad padding of cipher after upgrade
Our old forum is archived, you can access your thread here:
https://old-community.appsmith.com/t/malformed-gitauth-breaks-instance/2222
The resolution in the thread was to update to the latest version of Appsmith.
You said earlier that you upgraded and then downgraded again. Can you elaborate
on what happened there?
Site reports internal error: java.lang.IllegalStateException: Unable to invoke Cipher due to bad padding at org.springframework.security.crypto.encrypt.CipherUtils.doFinal(CipherUtils.java:141) Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: Error has been observed at the following site(s): *__checkpoint ⇢ Handler com...
it was 1.9.12
then upgraded to 1.9.16
errors as above
then downgraded to 1.9.12 to see if that would help
errors continued as above
upgraded via applying a helm chart with the image.tag value updated from 1.9.12 to 1.9.16
Thank you for the clarification.
I've forwarded the logs and additional information to our engineers
Please give us some time to look into this.
This error is being investigated by the team. Until we figure out the root
cause, please reset the database credentials, as this workaround should get you
unblocked.
how do i "reset the database credentials"?
do you perhaps mean "create a new mongodb database and start over again"?
I’m checking with the team to clarify that.
Please follow these steps:
- Connect to the local mongo DB server that is used by Appsmith
- Run query:
use appsmith - Then you'll need to run this query:
db.datasource.updateMany({}, {$unset: {"datasourceConfiguration.authentication":1}})
We can arrange a call if you need assistance here.
it's a remote
db.datasource.updateMany({}, {$unset:
{"datasourceConfiguration.authentication":1}}){ acknowledged: true, insertedId: null, matchedCount: 13, modifiedCount: 9, upsertedCount: 0}use appsmith'switched to db appsmith'db.datasource.updateMany({}, {$unset:
{"datasourceConfiguration.authentication":1}})
{
acknowledged: true,
insertedId: null,
matchedCount: 13,
modifiedCount: 9,
upsertedCount: 0
}
no impact to appsmith functionality
i'm not quite sure how we'd expect this to impact gitAuth