skariko

joined 4 years ago
[โ€“] [email protected] 2 points 1 year ago (1 children)

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.

[โ€“] [email protected] 15 points 1 year ago* (last edited 1 year ago)

well, indeed it could be just that. I just checked and it's size is 15GB ๐Ÿ˜ฑ

63
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

hello, on my server on which only Lemmy is running, I don't understand why it fills up space all the time. Every day it increases by about 1GB thus risking reaching the limit after a short time.

It is not the images' fault because there is a size limit for uploading and they are also transformed into .webp.

The docker-compose file is the one from Ansible 0.18.2 with the limits for loggin already in it (max-size 50m, max-file 4).

What could it be? Is there anything in particular that I can check?

Thanks!

28% - 40G (3 July)
29% - 42G (4 July)
30% - 43G (5 July)
31% - 44G (6 July)
36% - 51G (10 July)
37% - 52G (11 July)
37% - 53G (12 July)
39% - 55G (13 July)
39% - 56G (14 July)
[โ€“] [email protected] 2 points 1 year ago (1 children)

Thanks, will try it ๐Ÿ‘

 

hello, does anyone know if there is a bot to automatically post to certain Lemmy communities from an RSS feed?

I found this: https://github.com/Ategon/Lemmy-Mega-Bot but it says it is not compatible with Lemmy's new API.

[โ€“] [email protected] 2 points 1 year ago

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.

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago)

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 ๐Ÿ™ˆ

[โ€“] [email protected] 1 points 1 year ago (1 children)

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

4
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

hi, I installed a year ago lemmy via Ansible, then all the upgrades I always did by changing only the docker-compose.yml file.

Today I tried to upgrade from version 0.17.4 to 0.18 by changing the docker-compose.yml file but the site doesn't work.

The only error I have is:

Starting http server at 0.0.0.0:8536
lemmy_1 | the thread 'actix-rt|system:0|arbiter:0' panicked for 'No auth header for picture access', crates/routes/src/images.rs:138:8
lemmy_1 | note: run with environment variable `RUST_BACKTRACE=1` to display a backtrace
lemmy_1 | thread 'actix-rt|system:0|arbiter:0' panicking about 'No auth header for picture access', crates/routes/src/images.rs:138:8
lemmy_1 | thread 'actix-rt|system:0|arbiter:0' panicking over 'No auth header for picture access', crates/routes/src/images.rs:138:8

Thanks.

[โ€“] [email protected] 1 points 2 years ago

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.

0
Upgrade error (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 

Hello, I am trying to update from 0.16.3 to 0.16.5 with Ansible.

It is on my test instance, i use this:

git pull

and

ansible-playbook -vvv -u MYUSERNAME -k -K -i inventory/hosts lemmy.yml --become

It does everything with no error but when I try to visit the website i receive:

404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy

Could the problem be that I am using the backend (on different folders) multiple instances of lemmy?

 

Does anyone know if it is possible to create a new community on another lemmy instance using my lemmy.ml account or do I have to necessarily create a new user on the new instance?

And if the community is already created, is it possible to add moderators from other instances or do community moderators have to be registered to that instance?

[โ€“] [email protected] 1 points 2 years ago (2 children)

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

Thanks for the help!

[โ€“] [email protected] 1 points 2 years ago (4 children)

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: "[email protected]"
    tls_type: "none"
  }
[โ€“] [email protected] 2 points 2 years ago* (last edited 2 years ago) (6 children)

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?

 

Hello! I managed to set up an instance quite easily with Ansible, only problem now is that I can't send emails in any way!

If I leave the default configuration (postfix: 25) and try to ask for a password reset, it tells me it sent it but nothing really comes.

I then thought of using an external SMTP, since I have it available together with the domain.

If I put: "smtps.aruba.it" then adding smtp_login and smtp_password when I try to send an email I get an error with only written: "465".

If I add the port to the SMTP server like this: "smtps.aruba.it:465" and also adding in "tls_type: tls" the server freezes for 5 minutes, does not send anything and I do not receive any errors.

I'm definitely doing something wrong but what? Where can I look?

Thanks!

 

Hello, trying to use Ansible https://github.com/LemmyNet/lemmy-ansible to install Lemmy on a OVH VPS.

  • Configured DNS and ping it is ok.
  • I can reach the server with a sudo user on SSH

Installed Ansible on my local machine and follow the steps.

When i execute:

$ ansible-playbook -i inventory/hosts lemmy.yml

I have this error (I replaced for this help request real username and real ip address)

PLAY [all] ************************************************************************************************************************************************************************************************************

TASK [check lemmy_base_dir] *******************************************************************************************************************************************************************************************
skipping: [myuser@myip]

TASK [install python for Ansible] *************************************************************************************************************************************************************************************
fatal: [myuser@myip]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: myuser@myip: Permission denied (publickey,password).", "unreachable": true}

PLAY RECAP ************************************************************************************************************************************************************************************************************
myuser@myip      : ok=0    changed=0    unreachable=1    failed=0    skipped=1    rescued=0    ignored=0

What am i missing?

 

Hello everyone!

I am trying to add a community RSS to my RSS reader but it always give me error, on any RSS reader!

Like this: https://lemmy.ml/feeds/c/asklemmy.xml?sort=Active it can't be added to my RSS reader :(

What am I doing wrong? Is there another RSS link?

Thanks!