4·
17 days agoI just geo-restrict my server to my country, certain services I’ll run an ip-blacklist and only whitelist the known few networks.
Works okay I suppose, kills the need for a WAF, haven’t had any issues with it.
- 3 Posts
- 12 Comments
Joined 10 months ago
Cake day: February 8th, 2025
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Should put a note on your blog that Lidarr’s Metadata database is being rebuilt, currently the Lidarr APi spits a bunch of 5xx errors when searching for artists/albums/etc.
https://github.com/Lidarr/Lidarr/issues/5498
If you currently have a library on the stable build the Lidarr team could use some help building the cache, they made this tool:
https://github.com/DeviantEng/lidarr-cache-warmer
It’ll search every artist in your Lidarr library so that the new database has a cache to quickly call upon.
Something else must be wrong then because I just copied and pasted that onto my raspberry pi and was able to start the container without issue, are you sure you’re using the tag properly?
user@raspberrypi:~/test $ sudo docker compose up [+] Running 10/10 ✔ lidarr Pulled 22.0s ✔ 995f2a46b147 Pull complete 2.7s ✔ e1cde46db0e1 Pull complete 3.1s ✔ acaee427f4c7 Pull complete 3.5s ✔ 255c3937324a Pull complete 4.1s ✔ edec534df16f Pull complete 4.6s ✔ b163a490af0b Pull complete 6.3s ✔ bd4af268fa91 Pull complete 6.8s ✔ ff4dab968553 Pull complete 14.9s ✔ 004112d930a4 Pull complete 15.3s [+] Running 2/2 ✔ Network test_default Created 0.2s ✔ Container lidarr Created 4.0s Attaching to lidarr lidarr | [migrations] started lidarr | [migrations] no migrations found lidarr | ─────────────────────────────────────── lidarr | lidarr | ██╗ ███████╗██╗ ██████╗ lidarr | ██║ ██╔════╝██║██╔═══██╗ lidarr | ██║ ███████╗██║██║ ██║ lidarr | ██║ ╚════██║██║██║ ██║ lidarr | ███████╗███████║██║╚██████╔╝ lidarr | ╚══════╝╚══════╝╚═╝ ╚═════╝ lidarr | lidarr | Brought to you by linuxserver.io lidarr | ─────────────────────────────────────── lidarr | lidarr | To support the app dev(s) visit: lidarr | Lidarr: https://opencollective.com/lidarr lidarr | lidarr | To support LSIO projects visit: lidarr | https://www.linuxserver.io/donate/ lidarr | lidarr | ─────────────────────────────────────── lidarr | GID/UID lidarr | ─────────────────────────────────────── lidarr | lidarr | User UID: 1000 lidarr | User GID: 1000 lidarr | ─────────────────────────────────────── lidarr | Linuxserver.io version: 2.12.4.4658-ls50 lidarr | Build-date: 2025-08-20T02:50:40+00:00 lidarr | ─────────────────────────────────────── lidarr | lidarr | [custom-init] No custom files found, skipping... lidarr | [Info] Bootstrap: Starting Lidarr - /app/lidarr/bin/Lidarr - Version 2.12.4.4658 lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config] lidarr | [Debug] Bootstrap: Console selected lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config] lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config] lidarr | [Warn] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager: No XML encryptor configured. Key {bff9bf8a-f5db-4092-9ada-c55e886ac294}
Make a
docker-compose.ymlfile and paste this into it:services: lidarr: container_name: lidarr hostname: lidarr ### Use custom docker network #networks: # - CustomNetworkName ports: - 8686:8686 image: lscr.io/linuxserver/lidarr:arm64v8-latest restart: unless-stopped volumes: - /path/to/lidarr/config:/config - /path/to/music:/music #optional - /path/to/downloads:/downloads #optional environment: - PGID=1000 - PUID=1000 healthcheck: test: curl --fail localhost:8686 || exit 1 interval: 60s retries: 5 start_period: 300s timeout: 2sThis should work for you, just change the volume mounts so that they associate with your setup and run
sudo docker compose up -dto start the container,sudo docker compose downto bring it down.LSIO documentation describes the
arm64v8-latesttag for their image.
I opted to remove Jellyfins default login form and require Keycloak for SSO, my Jellyfin instance is technically facing the internet but my reverse proxy has Fail2Ban in front of it blocking non-whitelisted IP’s, makes it easier to share with other people this way compared to having to explain VPN’s to non-tech savvy people,
This is absolutely possible as I do it myself however, executed entirely differently, my ASUS WRT Router with Merlin firmware handles the VPN server and it routes the IP range through my VPN provider (Proton), on the clients end their device see a Proton IP.
Didn’t have to mess with config files or anything, install the custom firmware and created a rule for the routing in the VPN Director.
(It’s an Asus RT-AX86U Pro - so fairly chunky in terms of spec)
I have your exact router make and model! I self host my own server with a domain on my home network and make use of the built in DDNS feature.
My domain registrar is Cloudflare so I have to use a custom script for DDNS, if you’re in the same boat I can provide the script.
I would suggest looking into Asus WRT Merlin Firmware, the custom firmware enables more functionality to your router.
Docker containers for
- Ghost
- Nginx Proxy Manager
When hosting a reverse proxy like Nginx, Traefik, SWAG, Pangolin, etc keep in mind you 80:80 and 443:443 ports need to be exposed to the host machine then you will forward those ports on your router. This will allow your reverse proxy to communicate with Lets Encrypt generating and verifying your SSL certificates.
deleted by creator
Taking a look at your
docker-compose.ymlI see this volume mount:volumes: - /volume1/SN/Docker/searxng-stack/searxng:/etc/searxng:rwWhereas
/volume1/SN/Docker/searxng-stack/searxngis the directory on your system docker is attempting to use to store the files inside the container from/etc/searxng.Example of a volume mount that’ll likely work better for you;
volumes: - /home/YourUser/docker/config/searxng:/etc/searxng:rwThe tilde (~) acts as your current users home directorynot owned by root and where docker persistent volumes should be stored.(aka: /home/YourUser)Edit: I feel like I was wrong here, given that your run
sudoindocker compose up -dthe tilde will likely not work here and instead point to the/rootdirectory instead. I’ve updated the above to reflect the appropriate directory for your volume mount.After making the change over to that directory and configuring SearXNG how you like re-create your docker container with
sudo docker compose up -d —force-recreateApologies for the poor formatting, typing this on mobile.
Edit:
Note: if you want to expose the port do not add the
127.0.0.1like how I have in mydocker-compose.yml.Edit 2: Corrected some things…
have you checked the directory & file permissions with
ls -la /Your/SearXNG/WorkingDir?The error in your log is telling you that the container does not have permission to that directory/file, you can essentially bypass this with
sudo chmod 777 /Your/SearXNG/WorkingDir/*andsudo chown 1000:1000 /Your/SearXNG/WorkingDir/*However, if you’re looking for security best practices this is not advisable but if all you care about is that it works it should be fine.
Late to the party but I decided to pickup a 13th gen ASUS NUC with an i7 over a prebuilt NAS, bought a couple external hard-disk bays setup Proxmox running a headless Debian 12 VM and almost everything runs great however, mistake was using Debian 12 because the Linux kernel is pretty far out of date and does not support the CPU properly.
deleted by creator
Upload to Proton Drive > Create share link > Share link
I don’t use Home Assistant personally as I also use Apple products, if you read into Homebridge it’s a piece of software that turns smart devices that are not HomeKit enabled devices into HomeKit enabled devices, and enables new functionality to devices that are already HomeKit enabled. Definitely worth considering.
This was significantly cheaper than converting all my Apple products into android products.
To quickly spin it up I would suggest reading into Docker and Docker compose, docker takes applications and containerizes them and lets them run over your network.