Thank you very much for resolving the issue. I would love to understand what i did wrong.
I tried deleting the nginx.conf and certs and let them be regenerated as you have described in other threads. Yet I did not manage to get nginx back up and running. Are there additional steps besides deleting cofings, restarting box, nginx and unbound?
Muchas Gracias for saving the day!
Now that Castopod has reached v 1.0 can we have it on Cloudron? That would be excellent. I wish I could help but I am not a programmer.
Alternatively, people who installed Castopod on LAMP-stack, is anyone willing to write a short tutorial?
Solution:
./bin/tootctl media remove
has an option
--days
which defaults to 7 days of not set.
Our instance is only 3 days old. Since i did not set the flag it defaulted to 7 days.
The system did everything right. There were no files as old or older than 7 days. Accordingly it did not delete anything. Computer smart.
I was able to delete the cached media files.
@jdaviescoates I had this thought. I consulted other Mastodon admins. They say, they can delete everything. This should not occur.
In a non-Docker installation it is apparently found under
config/settings.yml
and should look like this:
reserved_usernames:
- admin
- support
- help
- root
- webmaster
- administrator
- mod
- moderator
It would be good if admins were able to control this list.
@nebulon Thanks! If that´s the case, we will be patient and wait for it to find its way upstream.
@girish OK, I am restarting the restore process with 4GB. Thank you.
@girish Thanks. Postgresql has 768MB memory limit, shall i increase it temporarily to more?
@girish It is Mastodon. Cloudron version of the app is v1.8.3.
Which service is it? mongodb?
I had to restore an app from a backup. The backup was transferred successfully from the backup volume. Now I am stuck for quite a while at "Restoring addons". I don´t know if I should just wait longer or try again.
The app log does not show any new information.
What to do?
@nebulon Thanks! If that´s the case, we will be patient and wait for it to find its way upstream.
In a non-Docker installation it is apparently found under
config/settings.yml
and should look like this:
reserved_usernames:
- admin
- support
- help
- root
- webmaster
- administrator
- mod
- moderator
It would be good if admins were able to control this list.
Now that Castopod has reached v 1.0 can we have it on Cloudron? That would be excellent. I wish I could help but I am not a programmer.
Alternatively, people who installed Castopod on LAMP-stack, is anyone willing to write a short tutorial?
Thank you very much for resolving the issue. I would love to understand what i did wrong.
I tried deleting the nginx.conf and certs and let them be regenerated as you have described in other threads. Yet I did not manage to get nginx back up and running. Are there additional steps besides deleting cofings, restarting box, nginx and unbound?
Muchas Gracias for saving the day!
journalctl -u nginx -fa
gives me
Aug 19 10:50:42 1001364-346 systemd[1]: Starting nginx - high performance web server...
Aug 19 10:50:42 1001364-346 nginx[11878]: nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.myserver.com.key": PEM_read_bio_PrivateKey() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: ANY PRIVATE KEY)
Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.
Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Aug 19 10:50:42 1001364-346 systemd[1]: Stopped nginx - high performance web server.
Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Start request repeated too quickly.
Aug 19 10:50:42 1001364-346 systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 19 10:50:42 1001364-346 systemd[1]: Failed to start nginx - high performance web server.