Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 0 Posts
  • 79 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Mihon has a setting to flash the display when changing pages to reduce ghosting on e-ink displays.

    Which you shouldn’t use. E-ink refreshes are far more complex than simply flashing the screen a solid color, involving multiple steps to massage the e-ink in the panel into a sharp image. These are calculated and done by the e-ink display driver on any decent device, whenever the image on screen changes enough.

    Mihon also does the flash out of sync with the actual display refresh (if it’s set to occur on tap), CAUSING ghosting, instead of reducing it.

    If you can configure your e-ink device to do a full display refresh on tap, simply do that.

    In Mihon, just disable animations, and let the e-ink display driver handle display refreshes.




  • I’m not sure on the answer myself, but you did get one thing wrong.

    Even the oldest, sickest pet will still make an effort to keep themselves alive however they can: eating, drinking water, moving out of the way of danger, etc.

    No, they won’t.

    Plenty of illnesses cause apathy, dehydration, or loss of appetite.

    Causes vary from pain so intense moving is unbearable, or nausea so severe food is inedible. It can be mental, physical, easily treated, or incurable and eventually lethal.

    Either way, pets can and absolutely do choose inaction when miserable enough.


  • Then my first assumption is that the session token is not being correctly stored in kwallet. It can’t restore the session after kwallet is closed.

    You can open kwallet manager, and delete the wallet. This will prompt your system to re-create it next time you go to use something that needs it (wifi, nextcloud).

    This will allow you to essentially reset the default wallet.

    The typical settings for it are “blowfish” encryption with either a blank password (which encrypts nothing, but allows the wallet to always open reliably) or using the same password as your user (which allows the wallet to decrypt automatically upon login).

    Another user also commented with useful links, the arch wiki page on kwallet is also potentially useful.


  • In that case, something in is invalidating the login. Are you sure that it is happening due to leaving your LAN, and not just coinciding with that?

    Does restarting the laptop log you out, or temporarily disconnecting from the internet? Could you test by switching to a wifi hotspot on your phone, and switching back, for example?

    The client stores your session token in the OS credentials manager (kwallet for linux kde, for example) and the issue can lie there, as well.







  • I also need to work out how to do automatic certificate renewal and if that’s even worth doing

    This is what certbot is for. For example, with nginx, you just set up the webserver to be reachable via your domain.

    You then install and run certbot, and it will aquire, install and configure, and then set itself up to auto-renew, a certificate. All with just one command.

    With Nextcloud specifically I also don’t like the fact that you can’t change the domain after the initial setup

    Yes you can?

    I’ve done it thrice now.

    Is this some limitation of the docker AIO stack?




  • MentalEdge@sopuli.xyztoSelfhosted@lemmy.worldDo I need a NAS ?
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 month ago

    No sane NAS should work that way.

    Unless you have a giant raid array, where you need all the drives running at the same time on the same system, plugging in a single raid 1 member, for example, via usb to sata adapter, should let you access its contents just fine.

    Provided you’re on an OS that can read the file system. That can require some extra effort on windows.

    But yeah. Beware of the pre-built NASes. The vendor lock-in is real.


  • A part of it is concern.

    System administration on a system you’re planning to use remotely over the internet must be done right. Not being sure what you’re doing is how we all learn, but you really should be sure before exposing yourself to the internet.

    It’s not like experimenting with linux on a laptop. Self-hosting is usually about providing some sort of service for yourself, which if accessed by someone malicious, can be used to really hurt you.



  • I didn’t tho.

    You’re confusing my homelab with my dads OMV NAS that is running kopia as its only non-standard service because I wanted to use it as my off-site target.

    I wasn’t presenting OMV as the solution to all of OPs examples, I literally just commented to point out “hey this is kinda like hexos but foss”.

    To which you responded “lol no, there is no comparison”. Which is both untrue, and a rude way to go about saying anything.


  • I don’t use docker via a GUI. And I don’t run docker at all on the NAS running OMV.

    My backup solution is Kopia. Two servers, each running an instance that backs up local storage to the other.

    OP isn’t talking about a full homelab. If all you need is a home VPN and some network storage via SMB, OMV is fine.

    For my homelab, OMV would be clunky af. For the NAS at my dad’s end, it’s ideal.