View Issue Details

This issue affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
20252Bug reportsSurvey takingpublic2026-10-23 12:20
Reporterjweberhofer Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status resolvedResolutionfixed 
Summary20252: Finalizing a larger survey results in a "wrong decryption key" message
Description

2025/09/02 09:21:08 [error] [exception.SodiumException] SodiumException: Falscher Entschlüsselungsschlüssel! Der Entschlüsselungsschlüssel hat sich seit dem letzten Speichern dieser Daten geändert, sodass Daten nicht entschlüsselt werden können. Bitte nutze unser Handbuch unter https://www.limesurvey.org/manual/Data_encryption#Errors. in /mypath/limesurvey/application/core/LSSodium.php:141
Stack trace:
#0 /mypath/limesurvey/application/models/LSActiveRecord.php(379): LSSodium->decrypt()
#1 /mypath/limesurvey/application/core/LimeMailer.php(145): LSActiveRecord::decryptSingle()
#2 /mypath/limesurvey/application/core/LimeMailer.php(253): LimeMailer->__construct()
#3 /mypath/limesurvey/application/helpers/frontend_helper.php(469): LimeMailer::getInstance()
#4 /mypath/limesurvey/application/helpers/SurveyRuntimeHelper.php(1308): sendSubmitNotifications()
#5 /mypath/limesurvey/application/helpers/SurveyRuntimeHelper.php(241): SurveyRuntimeHelper->moveSubmitIfNeeded()
#6 /mypath/limesurvey/application/controllers/survey/SurveyIndex.php(668): SurveyRuntimeHelper->run()
#7 /mypath/limesurvey/application/controllers/survey/SurveyIndex.php(22): SurveyIndex->action()
#8 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/actions/CAction.php(76): SurveyIndex->run()
#9 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(308): CAction->runWithParams()
#10 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(286): CController->runAction()
#11 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/CController.php(265): CController->runActionWithFilters()
#12 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/CWebApplication.php(282): CController->run()
#13 /mypath/limesurvey/vendor/yiisoft/yii/framework/web/CWebApplication.php(141): CWebApplication->runController()
#14 /mypath/limesurvey/vendor/yiisoft/yii/framework/base/CApplication.php(185): CWebApplication->processRequest()
#15 /mypath/limesurvey/index.php(161): CApplication->run()
#16 {main}
REQUEST_URI=/limesurvey/index.php/666191

Steps To Reproduce

Steps to reproduce

The user processes a longer survey with multiple pages using it's token to access the survey . Upon saving on the last page, the user sees an error messages containing the text visible above. However the saved result entry has status 'completed'.

Expected result

User should not see the message.

Actual result

User sees error message with SodiumException

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)6.15.10+250901
I will donate to the project if issue is resolvedNo
BrowserEdge
Database type & versionMariaDB 10.3.39
Server OS (if known)openSUSE
Webserver software & version (if known)Apache
PHP Version8.2.29
Git branch / Pull Request URL

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2026-10-23 12:20

administrator   ~86714

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=40989

Related Changesets

LimeSurvey: master b89018b2

2026-10-23 12:19

c_schmitz


Details Diff
Fixed issue 20252: Respondents got a "Wrong decryption key" error at the end of the survey if the stored SMTP password could not be decrypted
Dev The SMTP password is now only decrypted when SMTP is used; if decryption fails, it is logged and the email fails like any other send error
Affected Issues
20252
mod - application/core/LimeMailer.php Diff File

Issue History

Date Modified Username Field Change
2025-09-02 13:16 jweberhofer New Issue
2026-10-23 12:20 c_schmitz Changeset attached => LimeSurvey master b89018b2
2026-10-23 12:20 c_schmitz Note Added: 86714
2026-10-23 12:20 c_schmitz Assigned To => c_schmitz
2026-10-23 12:20 c_schmitz Status new => resolved
2026-10-23 12:20 c_schmitz Resolution open => fixed
2026-10-23 12:20 c_schmitz Bug heat 0 => 2