The one reserved for residential usage is home.arpa
.
The one reserved for residential usage is home.arpa
.
Extra content in exchange for an upvote 🤔
Hopefully there’s more research done. It doesn’t sound like it’s “absolutely carcinogenic”.
The “radiofrequency electromagnetic fields” associated with using mobile phones are “possibly cancer-causing”. Like aspartame, this means there is either limited evidence they can cause cancer in humans, sufficient evidence in animals, or strong evidence about the characteristics.
That’s awesome, glad you were able to find a solution!
Maybe an issue with ram? Could be loose, dusty, going bad.
It sounds pretty awesome. Just wondering if adding additional complexity to the setup is worth it to obfuscate my home IP. Easily setting up redundancy is a good feature in that regard though.
Oooh thanks for the tip about frp
. Interesting.
It really depends on the company that you use to manage the domain’s DNS. As long as they have an API to update DNS records…
For example, I can have my domain at Porkbun and have its DNS managed at Cloudflare. Cloudflare allows updating DNS records via API…so there’s programs to update it. Some routers even support it.
Worst case, you can set up a service like duckdns and have your domain, via cname, point to the duck DNS subdomain.
There’s options.
I had found an old post which indicates that post thumbnails are cached. So I guess there’s that.
In case you didn’t see it, the OP of this thread realized they didn’t setup their pictrs
API key… so I guess it’s possible to omit that and lemmy should still work. Not sure about the downsides.
Don’t quote me on it but I think it, besides handling image uploads, caches thumbnails for link posts.
Can you put your own router behind, what I presume, is the ISP router? Then you can manage DHCP and IP address reservation.
Did you configure the pictrs API keys for Lemmy and for pictrs?
If they’re not configured then I could see Lemmy not even using pictrs.
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.
Sounds like maybe the depends_on
service property might be useful?
https://docs.docker.com/compose/compose-file/05-services/#depends_on
Making NPM depend on the restarting container might make it restart too when that happens. 🤔
https://www.rfc-editor.org/rfc/rfc8375.html