

6·
3 hours agoWell done on getting it up and running, federation seems to be working https://moplemmy.fyi/instances & https://phiresky.github.io/lemmy-federation-state/site?domain=moplemmy.fyi
You shouldn’t have to put instances in the Allowed Instances, just use blocked list for stuff you dont want to see
Yes email is a pain in the arse. More so if you are having to deal with dynamic IPs
Now just wait for the scrapers to turn up. Both Dave (lemmy.nz) and I are getting well in excess of 500k requests from content scrapers per day atm and they are tyring to pull in whole comment trees and walk through all posters.
Have a look at Iocaine to help tarpit some of them if you dont want to route through something like cloudflare.

Back up the server then work through:
Just follow the guide https://iocaine.madhouse-project.org/documentation/3/getting-started/ Bind the iocaine service to 0.0.0.0:42069
cat /opt/iocaine/etc/iocaine/config.d/00-server.txt.kdl http-server default { bind "0.0.0.0:42069" use handler-from=default }expose interface to Docker (make sure not to expose it to the world).
sudo iptables -I INPUT 4 \ -s 172.18.0.0/16 \ -d 172.18.0.1 \ -p tcp --dport 42069 \ -j ACCEPTadd the interface to the proxy service in a custom/docker-compose.yml.template
proxy: {{COMPOSE_CADDY_IMAGE}} env_file: - ./caddy.env - {{ CADDY_EXTRA_ENV }} volumes: - ./caddy/Caddyfile:/etc/caddy/Caddyfile:ro - caddy_data:/data - caddy_config:/config extra_hosts: - "host.docker.internal:172.18.0.1" ...add iocaine to caddy in a custom/Caddyfile.template
{$LEMMY_HOSTNAME} { import caddy-common ###################################### ########## iocaine code ########## @read method GET HEAD reverse_proxy @read host.docker.internal:42069 { @fallback status 421 handle_response @fallback } ...rebuild all the docler images (at least the caddy one ./deploy.sh -f) and test
I think that should work