[–] [S] 3 points 2 weeks ago*

@otter@lemmy.ca @hal@piefed.nz thanks for the encouragement to try Anubis.

The instance is now running using the Ansible playbook, with Anubis enabled. I changed the server back to non-private (which didn't help, anyway).

I've been interested in switching to running Lemmy via the Ansible playbook for a long time, but now that I've done it I miss "my way"! I'll either have to go back to "my way" or fork the playbook and learn how to make ansible do things how I like it.

Mostly, I need to figure out how to have everything go through Nginx Proxy Manager instead of the built in nginx container. I like having everything on an nginx docker network so they can use hostnames to find each other instead of IP addresses.

  • source
  • [–] [S] 4 points 2 weeks ago (2 children)

    I've heard mostly good things about Anubis, but I've also heard it can be hard to get it right. I've never looked into it so I'm not sure what people are referring to... maybe the balance between blocking lots of bots but still letting humans through?

    This Lemmy instance is mostly sticking around for posterity, so hopefully Private Instance cuts down on the B.S. so I don't have to think about it any further!

  • source
  • parent
  • context
  •  

    LLM scrapers and bots are a continuing challenge. Lemmy is not behind Cloudflare and custom filtering rules using NGINX only gets you so far.

    I'm trying the setting called "Private Instance".

    It's my understanding that all this does is require a user to be logged in to use the instance. This will hopefully cut down or stop the constant scraping. Preliminary signs are that it helps a ton.

    • walden
    [–] 8 points 1 year ago (1 child)

    Vanilla nginx is still too far over my head, but Nginx Proxy Manager makes easy work of it.

    A lot of people like Caddy but I've never tried it. The config files are much simpler and it auto-renews certificates (but so does Nginx Proxy Manager).

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (1 child)

    A while ago I decided that BTH only works well for 1 device (using wireguard at least) at a time.

    I messed around and made different profiles (not sure of the actual name) for each device and that solved my problems.

    Worth a shot.

  • source
  • [–] 8 points 1 year ago

    That's pretty neat. I was expecting something basic like "pay it off every month and there's no interest", but this was much more interesting.

    It's a method that web pages use to make sure you didn't make a typo in the number.

  • source
  • [–] 2 points 1 year ago

    Are you familiar with Mikrotik? If you're located in the USA, you can browse Streakwave, Roc-Noc, Baltic Networks and others to see about pricing.

    I only did a little research and this one seems to fit your needs (8 PoE/PoE+ ports, low power consumption) https://mikrotik.com/product/css610_8p_2s_in

    One downside to their more inexpensive switches is they run SwitchOS instead of RouterOS as their software. You can still accomplish tons of stuff, but some people have concerns that RouterOS has sort of been left to die without many updates in the works.

    You can also use their routers as switches. I do that with the PoE version of the RB5009 https://mikrotik.com/product/rb5009upr_s_in. It's more expensive than the switch I mentioned, but I like it for the form factor and that it runs RouterOS.

    You seem to be tech savy enough so you can figure out how to configure it as a switch. Basically you just add all of the ports to Bridge.

  • source
  •  

    Hello everyone,

    I'm keen on starting a PieFed instance to maybe replace our Lemmy instance one day. One thing I wasn't able to figure out was the various ways to store images. With Lemmy, images and thumbnails take up a large portion of whatever storage you have, so using Object Storage (like Cloudflair R2, Backblaze B2, Amazon S3) is the way to go to save money.

    Is that possible with PieFed yet?

    Thanks.

    RouterOS 7.19.2 Changelog (sub.wetshaving.social)
     

    What's new in 7.19.2 (2025-Jun-20 10:55):

    *) bfd - fixed socket leak;
    *) bgp - fixed withdraw when input.accept-nlri is non-existent;
    *) btest - properly close unsuccessful TCP test sockets;
    *) console - added prompt to /disk/format command;
    *) disk - do not allow to start Btrfs replace command when a Btrfs replace process is already running;
    *) disk - improve disk file system detection;
    *) hotspot - allow only "http:" and "https:" schemas in dst field;
    *) iot - added LoRa interface recovery mechanism;
    *) iot - LoRa stability improvement;
    *) iot - LR8G/9G firmware update;
    *) ip-service - fixed "print count-only interval" when dynamic entries are added (introduced in v7.19);
    *) ip-service - fixed setting services by name (introduced in v7.19);
    *) ipsec - fixed responder on key exchange compute failure (introduced in v7.19);
    *) ipv6 - do not show IPv6 FastPath as active when connection tracking or IPsec is used;
    *) l2tp-ether - fixed interface creation/removal process;
    *) lte - added support for R11e-LTE6 v039 firmware release;
    *) lte - do not dial further if modem detects eSIM without profiles;
    *) lte - fixed eSIM management function for mmips and mipsbe architecture CPUs;
    *) lte - fixed eSIM provisioning for servers that do not send content-length in the HTTP response;
    *) route - fixed destination ordering for SNMP;
    *) route - fixed SNMP probing of IPv6 routes;
    *) route - make routing table print faster with hw-offload, gateway and blackhole queries;
    *) switch - fixed ACL rules when ports are not specified (fixes dynamic rules for RoMON);
    *) switch - fixed advertise and speed settings for ether1 on RB5009 (introduced in v7.19.1);
    *) webfig - improved screen reader support for WiFi fields in Quickset;
    *) webfig - make combobox accessible to screen readers;
    *) webfig - more space to branding logo;
    *) wifi-qcom - fixed beacon loss issues and improved stability for IPQ-6018;
    *) wifi-qcom - improved regulatory compliance;
    *) winbox - fixed "Last Topology Change" for bridge port monitor;

    view more: next ›