#internal server error when logging in

1 messages · Page 1 of 1 (latest)

frozen torrent
#

After user logs in the page load for a while and then shows the screenshot.
i have traced the error to
[2024-11-26 09:32:01,222] [email protected], sessionId=46d0997c-f0f6-422e-99ed-074050374431, thread=lettuce-epollEventLoop-10-2, requ>[2024-11-26 09:32:02,089] [email protected], sessionId=46d0997c-f0f6-422e-99ed-074050374431, thread=nioEventLoopGroup-3-4, requestId=>org.springframework.dao.InvalidDataAccessResourceUsageException: Unexpected exception
at org.springframework.data.mongodb.core.MongoExceptionTranslator.translateExceptionIfPossible(MongoExceptionTranslator.java:95)
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
*__checkpoint ⇢ Handler com.appsmith.server.controllers.ApplicationController#getAllApplicationsForHome() [DispatcherHandler]
I am using self hosted Appsmith Community v1.9.61

error.png
drowsy leafBOT
#

It seems like you're encountering a org.springframework.dao.InvalidDataAccessResourceUsageException related to MongoDB in your self-hosted Appsmith instance. This error often indicates an issue with accessing the database, possibly due to incorrect configuration or connectivity issues.

Here are a few steps you can take to troubleshoot and resolve this issue:

  1. Check MongoDB Connection: Ensure that your MongoDB instance is running and accessible from the Appsmith server. Verify the connection string in your environment variables, specifically APPSMITH_MONGODB_URI, to ensure it is correct?5:13?source?.

  2. Review MongoDB Logs: Check the MongoDB logs for any errors that might indicate why the connection is failing. This can provide more specific information about the issue?5:13?source?.

  3. Environment Variables: Double-check all environment variables related to MongoDB configuration to ensure they are set correctly?5:13?source?.

  4. Network Accessibility: Make sure there are no network issues preventing the Appsmith server from reaching the MongoDB instance. This includes checking firewall rules and network configurations?5:13?source?.

  5. Upgrade or Downgrade: If the issue started after an upgrade, consider downgrading to a previous stable version. Conversely, if you are on an older version, upgrading might resolve the issue?5:14?source?.

If these steps do not resolve the issue, it might be beneficial to reach out to Appsmith support for further assistance.

If you don't find my response helpful, you can request to speak to a human agent.