What app is this about, and its version: GoToSocial .22.0-ynh.01
What YunoHost version are you running: 12.1.40.1
What type of hardware are you using: Old laptop or computer
i updated the app and i haven’t got new posts or been able to post anything since. the landing site still functions - shows the total number of posts, instances federated with, etc.
tried force upgrading, didn’t fix. thoughts?
n/a
I had the same thing happen (more or less). I updated and my landing page and account details were ok.
-It seems all my posts had disappeared (my post count was zero). 1 user with 0 posts.
-I was not able to post anything. I got an internal server error. Sorry I forgot to log all the errors etc.
My band-aid solution was to try to restore the back up Yunohost had made pre update. But then I got the error it couldn’t restore because there was already an GTS instance…. So further band-aid was to delete my GTS instance and hope for the best with the restore. The restore put everything back to rights but with the ‘older version’ (pre-update). So back to square one. Was hoping there would be some news. 
As a band-aid solution try upgrading to 0.21.3 as it fixes CVE
sudo yunohost app upgrade gotosocial -u https://github.com/YunoHost-Apps/gotosocial_ynh/tree/b4cb369a2015b2f1f279bc0d1117eb2ce9829428
As to error after upgrade - this needs more investigation, I’ll file a bug on GH for tracking
EDIT: tracking: 0.22.0 wipes data on install (?) · Issue #221 · YunoHost-Apps/gotosocial_ynh · GitHub
I’m running into the same issue here, no new toots are coming in. I tried the band-aid solution but it didn’t work.
I’m wondering if I need to re-install or start over, or wait for an update if it will get fixed with the next release? 
I don’t think the problem is related to recent update (or if it is the band aid revert to 0.21.3 should have helped).
Is gotosocial service up and running? Are logs indicating any issues? Check under webadmin->tools->services
The `gotosocial` service is up and running, here's the last bit of the logs:
Jul 14 15:33:35 systemd[1]: gotosocial__3.service: Consumed 20min 20.263s CPU time.
Jul 14 15:33:49 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 15:33:49 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:49 systemd[1]: gotosocial__3.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 14 15:33:49 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Scheduled restart job, restart counter is at 1.
Jul 14 15:33:50 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 15:33:50 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Scheduled restart job, restart counter is at 2.
Jul 14 15:33:50 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 15:33:50 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Scheduled restart job, restart counter is at 3.
Jul 14 15:33:50 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 15:33:50 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 14 15:33:50 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Scheduled restart job, restart counter is at 4.
Jul 14 15:33:51 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:51 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 15:33:51 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Scheduled restart job, restart counter is at 5.
Jul 14 15:33:51 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Start request repeated too quickly.
Jul 14 15:33:51 systemd[1]: gotosocial__3.service: Failed with result 'exit-code'.
Jul 14 15:33:51 systemd[1]: Failed to start gotosocial__3.service - GoToSocial Server.
Jul 14 16:11:52 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 14 16:11:52 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 21 13:43:05 systemd[1]: Stopping gotosocial__3.service - GoToSocial Server...
Jul 21 13:43:05 systemd[1]: gotosocial__3.service: Deactivated successfully.
Jul 21 13:43:05 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 21 13:43:05 systemd[1]: gotosocial__3.service: Consumed 30min 56.774s CPU time.
Jul 21 13:43:11 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 21 13:43:11 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
Jul 21 13:49:38 systemd[1]: Stopping gotosocial__3.service - GoToSocial Server...
Jul 21 13:49:38 systemd[1]: gotosocial__3.service: Deactivated successfully.
Jul 21 13:49:38 systemd[1]: Stopped gotosocial__3.service - GoToSocial Server.
Jul 21 13:49:38 systemd[1]: gotosocial__3.service: Consumed 4.489s CPU time.
Jul 21 13:49:52 systemd[1]: Starting gotosocial__3.service - GoToSocial Server...
Jul 21 13:49:52 systemd[1]: Started gotosocial__3.service - GoToSocial Server.
The last toots I have are from the 8th 9th of July. I tried stopping/starting the service and I also tried to force-upgrade.
The service itself should show some logs. If not stop the service and try
sudo systemctl stop gotosocial
sudo yunohost app shell gotosocial
./gotosocial --config-path ./config.yaml server run
It should show server’s stdout, hopefully indicating some problems?
Okay, I tried that and this error is popping out to me:
insertStatus: error inserting status: ERROR: null value in column “federated” of relation “statuses” violates not-null constraint (SQLSTATE 23502) (code=23502)"
What if you run
sudo systemctl stop gotosocial
sudo yunohost app shell gotosocial
./gotosocial --config-path ./config.yaml migrations run
?
Hmm, no migrations to run it seems:
timestamp=“21/07/2026 21:45:52.653” func=migration.Run level=INFO msg=“starting db service…”
timestamp=“21/07/2026 21:45:52.662” func=bundb.pgConn level=INFO msg=“connected to POSTGRES database”
timestamp=“21/07/2026 21:45:52.664” func=bundb.doMigration level=INFO msg=“there are no new migrations to run”
timestamp=“21/07/2026 21:45:52.665” func=bundb.(*basicDB).Close level=INFO msg=“closing db connection”
I think this is the issue I’m running into:
If I’m understanding this correctly, I need to roll back and update/migrate again. But my last backup is from 5 hours ago, I don’t have a backup for the original upgrade attempt…
Through some trial and error and help from AI (
), I managed to re-run part of the migration that failed, so it looks like I’m good now. Thanks for your help! I learned some stuff about YunoHost and GoToSocial! 
0.22.0 failed ( hastebin ), so I rolled back to 0.21.0 (I think).
After that I installed 0.21.3, which worked as expected.
Now I’ve tried to upgrade to 0.22.1, but then again, even if the service is running, I am unable to fetch updates. Here my log: hastebin
This is an arm64 VPS, YNH 12.1.40.1 (stable)
It’s still processing the migrations (40% done at the time you fetched the logs), give it a minute.
Thank you very much. I tried again, gave it some more time and it worked.
In my defence I’ll say that last time (0.21.0 to 0.22.0) I gave it a whole week and it didn’t work, so I thought it was going through the same!