Resolving DNSMASQ_WARN – Maximum number of concurrent DNS queries reached (max: 150)
|
1 2 3 4 5 |
#### EDIT SETTINGS dns-forward-max=5096 min-cache-ttl=300 rebind-domain-ok= #### END EDIT |
Giving LinkDing a whirl. It isn’t featured in any of the stores I’ve found, so I rolled my own. Here’s a sample YAML:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
name: courageous_kalyn services: main_app: cpu_shares: 10 command: [] deploy: resources: limits: memory: 256M image: sissbruecker/linkding labels: icon: https://icon.casaos.io/main/all/linkding.png ports: - target: 9090 published: "9090" protocol: tcp restart: unless-stopped volumes: - type: bind source: /DATA/AppData/linkding/data target: /etc/linkding/data devices: [] cap_add: [] environment: [] network_mode: bridge privileged: false container_name: "" hostname: "" x-casaos: author: self category: self hostname: "" icon: https://icon.casaos.io/main/all/linkding.png index: / port_map: "9090" scheme: http store_app_id: courageous_kalyn title: custom: LinkDing |
Once it’s up, hit the terminal and create a user with:
|
1 |
python manage.py createsuperuser --username=joe --email=joe@example.com |
From there it will prompt for a password.
I’m using Navidrome in CasaOS on a Pi for music right now and I like it quite a bit. The one thing irking me was that the network storage mounts you can define within CasaOS (Files > Location > Connect network storage) don’t persist. At least they don’t for me – every reboot or update and they’re gone.
I’ve gotten around this by creating a persistent mount within Raspbian utilizing CIFS.
SSH into your Pi, and go ahead and
|
1 |
sudo su |
to avoid having to sudo every line you input. First, make sure cifs-utils are installed (they should be, but still):
|
1 |
apt-get install cifs-utils |
Now create a credentials file for your mount to access using nano:
|
1 |
nano /etc/credfile |
Populate the credfile with the credentials necessary to access your Windows share:
|
1 2 3 |
username=user password=password domain=domain (if applicable) |
Save it, then set the appropriate permissions to keep it safe from prying eyes:
|
1 2 |
chown root: /etc/credfile chmod 600 /etc/credfile |
Create a mount directory on your Pi to link the share to:
|
1 |
mkdir /mnt/linux_sharename |
Now open fstab:
|
1 |
nano /etc/fstab |
Add your mount to the bottom of the file, changing the first path to the Windows share and the second to the mount path you created previously:
|
1 |
//WIN_SHARE_IP/share_name /mnt/linux_sharename cifs credentials=/etc/credfile,file_mode=0755,dir_mode=0755 0 0 |
Finally, reload the daemon:
|
1 |
systemctl daemon-reload |
And mount the share using the details you defined in fstab:
|
1 |
sudo mount /mnt/linux_sharename |
To confirm, cd to the share and confirm you can see the contents.
My Calibre Web installed via container in CasaOS decided to lose its admin account creds. To reset, access the container terminal from within CasaOS, navigate to:
|
1 |
/app/calibre-web |
and enter:
|
1 |
python3 cps.py -p /config/app.db -s admin:password |
Where password is your updated passy. If you try to use ‘password’ you’ll probably be kicked back for it not meeting complexity requirements.
I use my commercial host, Ionos, for websites, including creating subdomains for ones I’m hosting at home. However, I don’t pay for a static ip. I was using a Windows Scheduled Task to curl the necessary URLs to keep the IP updated, but I’m switching everything I can over to Linux, and a Pi.
Start by creating your .sh file and making it executable. I created dnsupdate.sh in my home dir on my Pi, and populated it with my curl calls. I did this via Nano. Then make it executable:
|
1 |
sudo chmod +x dnsupdate.sh |
Then I fired up cron by entering:
|
1 |
crontab -e |
It’s going to ask you for an editor on first use. I say, stick with Nano.
|
1 2 3 4 5 6 7 8 9 |
no crontab for root - using an empty one Select an editor. To change later, run 'select-editor'. 1. /bin/nano <---- easiest 2. /usr/bin/vim.tiny 3. /bin/ed Choose 1-3 [1]: 1 crontab: installing new crontab |
After this it will present you with a crontab file. Scroll to the bottom and enter:
|
1 |
0 * * * * /home/USERNAME/dnsupdate.sh |
This will run your sh file every hour at the top of the hour.
Save the file.
If you want to see what’s up with Cron, enter:
|
1 |
systemctl status cron |
If it’s running, it’ll show you the files – your sh file – in use by cron.
I installed ArchiveBox on CasaOS and came upon a problem – I couldn’t figure out what the default credentials are, or even if there were any, and I didn’t know how to generate them from the command line. ArchiveBox told me to create a new superuser by running
|
1 |
archivebox manage createsuperuser |
From the command line, but doing so within the container terminal resulted in this:
But I found my way into the container bash thusly:
|
1 |
grep -Rnw '/var/lib/docker/containers/' -e 'archivebox' |
|
1 |
9296e127fe81605cdd5dfb546b9a66eefef4ce5529423f45eaf89eba40507646 |
|
1 |
docker exec -u archivebox -it containerID bash |
|
1 |
archivebox manage createsuperuser |
Somewhere in my intertoobs wanderings I came across CasaOS and, given I had an idle Pi 4 laying around, I decided to poke at it. After all, if it works worth a damn it could help consolidate all the disparate systems I have running locally.
CasaOS is basically a slick Docker manager that rides atop another OS. Getting it up and running on the Pi with a fresh Raspbian install was painless. Simple configs, like mounting network shares, is a breeze. So far I have the following running in it:
