Yes I had considered that, but considering that ours is not a giant but moderate instance (a thousand subscribers) it seemed exaggerated to get to have 1GB occupied every day.

well, indeed it could be just that. I just checked and it’s size is 15GB 😱

Thanks, will try it 👍

My problem was that the Hetzner server was new and therefore certain ports were closed. I solved it by contacting Hetzner support and having them open the ports.

It seems to have been resolved: the problem was the private instance setting, as soon as I edited in the database and it worked again 🙈

I actually only used Ansible for the first installation, all subsequent ones I manually updated only the docker file and following the various instructions that were given only in this update it didn’t work.

If it helps I can post my current configuration file docker-compose.yml

edit:

maybe I need to try again to do an update through Ansible now?

Since it had always worked to update the docker-compose.yml file it seemed easier and more functional to do it this way but I don’t want to think that maybe the installation is now “tied” to Ansible.

I had to restore an old backup because in no way had the problem resolved itself.

If you’re interested on GitHub they suggested this to me: https://github.com/LemmyNet/lemmy/issues/2653#issuecomment-1380541659 unfortunately the suggestion came after I restored the backup and I couldn’t try it.

If you’ll try it let me know if it works or not!

Hello, I have the exact same problem as you, and it also happened to me at the time when my instance was running out of free space.

Did you by any chance solve it somehow?

same. Also preview does not seems to work

I tested from Mastodon but votes seems not works

test

Ahaha, tra un po’ questa comunità pensavo di cancellarla proprio per evitare confusioni ulteriori!

L’errore è averlo postato su lemmy.ml 😅

Found out just now what the problem was.

I am writing this to help others: the federation was active in that instance but it was also marked as a private instance. This gave no problems in using it until the update (probably because it is restarted and re-run Docker).

I removed the federation from the config file leaving only the private instance and it restarted immediately.

Hello, I just wanted to inform you that maybe LibreWolf updater is not working anymore because it is still stuck at version 99 while it has been several days since version 100 came out.

(don’t know how to contact the authr of the extension)

ottimo, non me ne ero accorto perché a me non dà errore. Si può leggere qui: https://archive.ph/16JTO

I have answered and find the solution here: https://lemmy.ml/post/258218/comment/176759

Thanks for the help!

I think i got it solved.

It was fault of being a new customer of Hetzner, ask them to make some tests and with port opens it’ll go!

yes, actually i tried ‘none’, ‘tls’ and ‘starttls’ but with no success. I tried with external SMTP because the default created by ansible does not work:

  email: {
    smtp_server: "postfix:25"
    smtp_from_address: "noreply@mydomain.it"
    tls_type: "none"
  }

It is the same thing that I thought. Unfortunately, if I try to manually force the port by writing smtps.aruba.it:465 as I said the server freezes for several minutes, goes to 504 and does not send any email.

So I can not understand if the port must be entered in another way (?) or if I have to install something on the server first to be able to send an email through an external SMTP as in this case?