Hi Jeremy,
That’s right, probably the rundeck-config.properties file content doesn’t match with the encryption expected from the backend side.
If your instance is DEB-based, you can check the /etc/rundeck directory and rename the rundeck-config.properties.dpkg-old file as the original file, take a look.
If your instance is RPM-based you can take a look at the /etc/rundeck directory and check if exist any difference between rundeck-config.properties (current version) and rundeck-config.properties.rpmnew files (generated by the new version), take a look.
Anyway, the easy way to bring back your files is under a good server backup policy.
Hope it helps!
Hi Jeremy,
Checking this, the file could contain the original 3.4.3 rundeck-config.properties content. Anyway, if you followed the upgrading process from the docs, the process will generate a .dpgk-old file. Weird.
Regards!