Alt account of [email protected]

  • 1 Post
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2025

help-circle

  • Kris@feddit.orgtoFediverse@lemmy.world•Slrpnk.net is down
    link
    fedilink
    English
    arrow-up
    4
    ·
    25 days ago

    I bought a chinese PiKVM copy last time it happened, but ran into issues with the usb otg connection which I procastrinated on to fix, so it currently only shares the screen but not the input. But I also connected it to the main router which is supposed to run the ssh tunnel and reverse-proxy eventually but right now those run on a seperare server and that one went down 🫠

    So yeah, I am victim of my own half finished stuff as well as security hardening that now locked myself out pretty much…



  • Kris@feddit.orgtoFediverse@lemmy.world•Slrpnk.net is down
    link
    fedilink
    English
    arrow-up
    7
    ·
    26 days ago

    Due to the LLM scrapers I have been thinking that I might have to move to a hybrid system of going through a VPS with only some storage and compute services on my home servers remaining. It is an annoying expense of about 20€/month that I was hoping to avoid, but it will give some other benefits like a fully fixed IP, IPv6 support and DDOS protection.

    In such a setup the service would degrade better, like images breaking, but the main service staying up when my home server goes down.

    But it is not something I can setup now that the service is already inaccessible.


  • Kris@feddit.orgtoFediverse@lemmy.world•Slrpnk.net is down
    link
    fedilink
    English
    arrow-up
    32
    ·
    26 days ago

    poVoq here. I am starting to think I am cursed, because everything works fine (or is at least fixable with a remote server restart) until the second I go on a longer business trip and can’t easily access the hardware.

    Remote access is mostly lost, but I was able to triangulate the issue and of course it is something I had on my list of potential issues, but as a low priority item 🫠 At least it isn’t the same problem again as in 2025.

    What exactly triggered the issue is unclear though. I was still able to access the reverse-proxy server yesterday (shortly before it went down) and tried to do some updates for that php security problem in a VM that runs on the same machine. I thought I had those covered, but there is a slight chance that it is related and someone chained another exploit to escape the VM.

    Anyways, it looks like the realistic / not overly optimistic scenario is that the server will stay down until christmas. I did have someone who could restart the servers on site until this summer, but they had to relocate to mainland Portugal for job reasons (tourism sector) and so they will also only return for christmas.

    So yeah, not great at all, and I will have to think more seriously about how compatible this kind of self-hosting is with my current job, which limits my access to the servers for a few weeks at least once a year. It was easier during the pandemic times when I started all this, as deployments were shorter and more seldom back then.















  • Regarding the price and all that, maybe that is an interesting discussion to have with the slrpnk.net community? And it would also be good to let slrpnk.net users know how the instance is being ran, what hardware, where, etc, so users can be an educated decision on whether they want to see an instance or not? Maybe providing that info on the sidebar would be nice?

    We have been very transparent about that and documented that in the wiki which is linked in the sidebar. But it seems few people ever read the Wiki and having it integrated like it is with Piefed would probably help.

    I agree that more admins with remote access would be good to have, and we have been working towards adding more (there are already more than one, who are not directly involved with slrpnk, but rather the mother project f-hub.org), but physical access will always be limited by the location (Azores) unless we move to an entirely different data-center (which in turn would make it hard for me to access the physical servers).


  • Yes, I also suspect that at a certain scale it would make a difference, but with a single Postgres database and no advanced clustering or so, the real-life performance metrics of a medium sized Lemmy instance strongly point to Postgres being the bottleneck and not the Python or Rust codebase of the rest of the software.