Magnetico VS algo

This is really neat. I'll need to check it out. A couple years ago I ran my own instance of Magnetico (https://github.com/boramalper/magnetico), but this project looks a lot more polished.

This is likely your best bet, but I'd recommend you use postgres over sqlite, this is however where development died so some features like search or stats aren't implemented while using pg as the db.

You can create decentralized bittorrent indexers though (see https://github.com/boramalper/magnetico as an example)! This means you can search for bittorrent files without having to rely on a centralized service (although building the index does require some time & storage space of course).

https://github.com/boramalper/magnetico

Someone else did this a while back, universe continues to exist.

I just get a rickroll gif on your link. Did you mean this project?

"Autonomous (self-hosted) BitTorrent DHT search engine suite."

https://github.com/boramalper/magnetico

Although I admit, that I would love to see a maintained DHT search solution (like magnetico or dhtcrawler2).

Yeah, you probably found it. Abandoned, yes, but not necessarily unfinished.

A magnet search is easy enough to self-host, I can provide you with instructions to self-host a clearnet magnet search engine over I2P in the meantime, but you can probably figure it out from this: https://github.com/boramalper/magnetico which is an easy to self-host DHT search engine.

Since we're already presuming you have a functional PFSense box with Wireguard installed and a VPS stood up, now you need to get Algo installed on the VPS. I'm not going to write this part out in detail, but basically you need to follow the procedures here to get Algo installed. However, *before* running ./algo you probably want to edit some of the config.cfg settings. I disabled IPSec (which saves a bunch of package installs and prevents a bunch of failures I saw on some of my VPSs), set my reduce_mtu setting to 80 just to prevent any MTU issues down the line, turned off DNS encryption, and renamed my users to the servers in question (for example: pfsense, vps_server, etc)

Check out the command line args for Auto1111, it talks about a gradio setup that can be accessed remotely. There's a time limit on gradio links though, I think. You could also set up a vpn that will allow you to access your PC remotely, then run A1111 with the --listen command and access it that way. I've done this with an Algo VPN on Azure and a Wireguard client for Windows for Android, but any VPN that lets you access your PC remotely would work.

One way you could try to get around is building your own VPN service, like this: https://github.com/trailofbits/algo/blob/master/README.md

Things I have tried so far: Clear network cache and reset adapters - IDK it fix aprevious problem I had https://github.com/trailofbits/algo/discussions/14504

(I can simply install Algo and get the Wireguard tunnel working, easy peasy... But from there, I can never get Plex port 32400 open... so I'm just trying from scratch now...)

Maybe try running algo vpn (following the road-warrior setup) in a VM instead? It has very light requirements. https://github.com/trailofbits/algo/blob/master/docs/deploy-to-ubuntu.md