I have recently updated my selfhosted instance (10 licences) from 6.0.10 to 6.2.13. Following procedure to migrate from severals configuration files to the one environnement file. My instance works but third party integration “email” doesn’t work anymore despite that before migration all worked fine.
Now, When i tried to test sending email in third party integration, i have just a “task_id invalid” message in the top of third party integration window.
I tried to reconfigure the email account without success.
When i look in the logs/dbtable_web.log, i’ve just “[WARNING] log.py[line:246] Bad Request: /api/v2.1/dtable-message-status/”
My .env file seems to work fine because i can receive system notifications emails.
Can you check two other log files for any error messages when trying to send a test email?
These are dtable_events_message.log and dtable-events.log (both inside /opt/seatable-server/seatable/logs/).
And did you use the previous value of the SECRET_KEY variable when migrating it from dtable_web_settings.py to an environment variable during the upgrade from v6.0 to v6.2?
Otherwise 3rd party account credentials cannot be decrypted.
I checked the content of the SECRET_KEY in the backup migration files (made by your upgrade script) and values are the same (with the .env running file).
This strongly indicates that the SECRET_KEY is not available inside the container.
I assume that your .env file contains a line like the following:
SECRET_KEY='...'
In addition, seatable-server.yml must contain the following:
services:
seatable-server:
# ...
environment:
# ...
- SECRET_KEY=${SECRET_KEY:?Variable is not set or empty}
# ...
Otherwise the variable is not available inside the seatable-server container.
Is it possible that you did not download the latest *.yml files as part of the upgrade process?
One word of caution: Modifying the secret key will invalidate all user sessions (i.e. users will be logged out) and any 3rd party account created with a different secret key will no longer be usable.
