The one reserved for residential usage is home.arpa
.
The one reserved for residential usage is home.arpa
.
Oops indeed. Lemmy needs a security audit 😬
Looks like lemmy.blahaj.zone is back
I’d wager you’re likely fine if you’re using a mobile app when the affected image loads. Also, it appears they’re stealing auth tokens… not passwords or anything. At worst they could impersonate you until your token expires… but you’re not a high value target unless you’re an admin of an instance.
What kind of terrible markdown editor allows adding onload scripts to images though… it’s insane.
If it’s onload
then simply viewing the image runs that script. Yikes.
Tough call, probably for the best. Hopefully it’s resolved soon.
I think that’s right on the money.
The sophistication is impressive, using emojis. Are people getting paid to find the vulnerabilities or are they just bored??
Connect is ridiculously stable and feature-complete for how new it is. Definitely deserves to be mentioned.
I’m pretty sure that error indicates nginx isn’t receiving a response from the upstream server (Lemmy and Lemmy-UI). So, either your upstream server isn’t responding to requests or nginx is misconfigured with the wrong upstream server 🤔
Yikes, I didn’t even know there was a wiki. Thank you!
Yeah I haven’t uploaded any images on my instance myself. So none of those images are mine. Might do some reading tomorrow and see if there’s any mention of this in the past on other communities. It’s not an emergency but I’m curious.
How are you keeping your pictrs
directory so small?
Mine is at about 5GB after two weeks with just a single user. 😬
This is awesome info. There should be a place to document all the nuance around hosting an instance plus some tips and tricks.
I’ve been using https://dnsomatic.com/ for a long while now. It updates Cloudflare which manages my DNS. It updates DNS at other providers too which is useful.
My router is able to send DDNS updates to it.
I feel like I’m missing something here. I’ve never needed to worry about docker container IPs.
I wonder why you want them to have fixed IPs. I guess I want to understand the problem it would solve.
If all you want to do is have the other containers use the pihole as DNS… they’d already be doing so if the server is using it as the DNS server.
At worst you’d need to provide
dns:
- <server IP where pihole is>
property to the services.
I welcome the return of forums. What a simpler time.
https://www.rfc-editor.org/rfc/rfc8375.html