What app is this about, and its version: synapse 1.53 What YunoHost version are you running: 12.1.40.1 What type of hardware are you using: Old laptop or computer
Describe your issue
Upgrading synapse failed due to connection issues.
Then restoring the backup also failed.
Apparently it has something to do with the go version.
Any help appreciated. Link to complete log below.
2026-07-16 04:52:58,463: DEBUG - + pushd /var/www/synapse/lk_jwt
2026-07-16 04:52:58,464: DEBUG - /var/www/synapse/lk_jwt /home/yunohost.backup/tmp/synapse-pre-upgrade2/apps/synapse/backup
2026-07-16 04:52:58,464: DEBUG - + ynh_hide_warnings ynh_exec_as_app go build -o lk-jwt-service .
2026-07-16 04:52:58,464: DEBUG - + ynh_exec_as_app go build -o lk-jwt-service .
2026-07-16 04:52:58,464: DEBUG - + sudo -u synapse env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin COREPACK_ENABLE_DOWNLOAD_PROMPT=0 NPM_CONFIG_UPDATE_NOTIFIER=false go build -o lk-jwt-service .
2026-07-16 04:52:58,489: DEBUG - go: errors parsing go.mod:
2026-07-16 04:52:58,489: DEBUG - /var/www/synapse/lk_jwt/go.mod:3: invalid go version '1.25.0': must match format 1.23
2026-07-16 04:52:58,489: DEBUG - /var/www/synapse/lk_jwt/go.mod:5: unknown directive: toolchain
2026-07-16 04:52:58,491: DEBUG - + ynh_exit_properly
2026-07-16 04:52:58,491: DEBUG - + [[ restore =~ ^install$|^upgrade$|^restore$ ]]
2026-07-16 04:52:59,096: ERROR - Could not restore synapse: An error occured inside the app restore script
Thanks for your reply - yes it seems very much like the same error related to lk_jwt. As one suggests on the link you provided I tried removing golang-go with apt and then apt autoremove as well, but it ends up missing go:
Info: DEBUG - env: ‘go’: No such file or directory
The correct solution is to not install manually with APT golang. It’s expected to be installed as a resource. So now is seem that it’s not installed expected. Maybe it would be interesting to:
Check if something exist in /opt/goenv/versions/ with the command ls /opt/goenv/versions/.
If there are anything it could have been removed at the remove so doing a restore with the option --no-remove-on-failure would help to understand what what is the state of the golang installation when it crash.
yes but it’s a bit more complicated, because it should be added in case /opt/goenv/versions/.. exist but it seem not existing, that’s why it’s not in the path.