RGB

joined 1 year ago
 

I'm not sure how to update properly to the new version without breaking my instance. I tried following the directions in the instructions but I'm not sure if I have to have my original ansible files when I first set up the instance or not. Can someone give me a simple step by step?

[–] RGB@lemmyfi.com 1 points 1 year ago

Could you go to lemmyfi.com from your browser and tell me if it works for you?

[–] RGB@lemmyfi.com 1 points 1 year ago

I tried it but it didn't work for me. I'm the instance admin btw. This is on my own instance.

4
submitted 1 year ago* (last edited 1 year ago) by RGB@lemmyfi.com to c/lemmy_support@lemmy.ml
 

Lemmy website on my instance won't load (connection times out) but I'm able to access it through apps. Any idea what's wrong?

Edit more info: it fails with error 504 gateway timeout

Edit: I guess it didn't work on a different network I was on. It wasn't blocked just unreachable. Will have to check my DNS.

[–] RGB@lemmyfi.com 3 points 1 year ago (1 children)

they might be. but they won't be able to log in to break stuff.

 

I made a mistake. I forgot to cahnge the setting after updating to screen for bots. This is getting out of hand. Luckily database commands aren't too hard.

[–] RGB@lemmyfi.com 0 points 1 year ago (1 children)

You have to delete them from local_users and person tables. Be careful with person table to not delete entries from users outside your Instance. It worked for me and fixed the user count in my sidebar.

[–] RGB@lemmyfi.com 0 points 1 year ago (3 children)

What worked for me is manually deleting those entries from the database through the console. Gotta delete it from the postgresql database if you don't have any real user sign ups during the spam sign ups, you can just delete all entries after a certain point. That's how I did it.

 

Just deleted over 800 users from my database that joined in the last few hours from obviously fake emails and botted usernames. Make sure to either close registration or have some sort of safety check in place because things are getting hairy out here.

 

Posting this just to let new instance admins who may have faced the same problem as me with email verification know a solution. It is important to set up SPF record so big email providers won't reject your email. All you have to do is configure the TXT entry in the DNS configuration of your domain name provider to include "v=spf1 mx -all"

Note: this won't prevent it from going to spam folder, that requires more verification, but this will at least allow emails to go through.

[–] RGB@lemmyfi.com 1 points 1 year ago

You're still subscribed. it's just visually broken.

[–] RGB@lemmyfi.com 1 points 1 year ago

Just keep an eye on the GitHub page if you want to stay updated at all times. Other than that just check up on your storage use from time to time. You can also set up a job to restart the server every once in a while but that's not really necessary.

[–] RGB@lemmyfi.com 1 points 1 year ago

This applies to any website. by visiting the website you give them your IP. the only way to mitigate this is to use a VPN.

 

A few times I've seen a user get banned in my instance when they got banned elsewhere. how does that work?

 

A lot of things aren't syncing well with other instances. I'm not sure what I did wrong. I used the ansible method. What should I check. I did the troubleshooting steps but that didn't help.

[–] RGB@lemmyfi.com 2 points 1 year ago

Pixel 6a. I really like the pixels but when they are rooted.