tried this

In the log in Ports in Use, connman was using port 53, which is needed by the pihole. I followed these instructions: https://wiki.archlinux.org/title/ConnMan#Avoiding_conflicts_with_local_DNS_server

in order to create the folder I had to use the command:

sudo mkdir /etc/systemd/system/connman.service.d/

Then to create the file I used:

sudo nano -w /etc/systemd/system/connman.service.d/disable_dns_proxy.conf

Then pasted in the text that it said into the file

[Service]
ExecStart=
ExecStart=/usr/bin/connmand -n --nodnsproxy

Then hit ctrl+X to exit, y to say I want to save it, and then enter to confirm saving with the filename.

still didn’t work until i did this as well. i think

sudo systemctl restart unbound

Couldn’t get tailscale working as an exit node on my pihole, really frustrating when wanting to use pihole blocking benefits away from home. If i enabled exit node then internet stopped working. After alot of messing around found out that somehow ‘enable packet forwarding’ and persistence were not occuring on the rpi but it was advertised as an exit node…..so SSH into the rpi…

enable packet forwarding

echo “net.ipv4.ip_forward=1” | sudo tee -a /etc/sysctl.d/99-forwarding.conf echo “net.ipv6.conf.all.forwarding=1” | sudo tee -a /etc/sysctl.d/99-forwarding.conf sudo sysctl –system

enable persistence

sudo systemctl enable tailscaled

…and all appears to be working again!

remember that my dns servers are running off pihole#1 .03 and pihole#2! .05

they had been running unbound but something screwed that up. unifi would be giving excellent wifi signal but no internet – i had to remove unbound via putty using ” sudo apt remove unbound ” and choose alternative upstream dns server. think i will leave unbound off for a while…..

the main reason for this i think is expressvpn managed to kill my internet even when the kill internet lock option was disabled. i had to do a complete network adapter reset

remember to reinstall tailscale but also found opera vpn wouldn#t work until tailscale stopped first……it’s always dns

deactivated for the moment. This is the plugin name in case i forget it again on agrimed

Wee reminder about the drive side being reverse threaded that i found on Reddit!

“The tool you need is a cartridge bottom bracket tool. They are specialized, but not too expensive. The Drive side (where the chain is) is reverse-threaded. (Righty-Loosey/Lefty-Tighty)

When you install a new bottom bracket, bottom out the drive side threads first, then install the non-drive side cup.”

Found a neat wee guide on Reddit for this – thanks to FFS!

Press Windows_logo_key + R to pop-up the Run command box and then type %localappdata%\qBittorrent and hit enter. You’ll get a folder and minimize it.

Again repeat the same process and this time type %appdata%\qBittorrent instead of %localappdata%\qBittorrent. You got another folder and now you have two separate qBittorrent folders.

Select and copy everything from the newly two opened folders and paste them to other two folders (1 for %localappdata%\qBittorrent and 1 for %appdata%\qBittorrent) and save the folders in a safe directory.

Restore Process

After installing, close qBittorrent by pressing Ctrl+Q.

Follow the previous steps again to open %localappdata%\qBittorrent folder.

Delete everything from that folder and copy everything from the backup we kept earlier for that folder.

Repeat same process for %appdata%\qbittorrent folder too.

Open qBittorrent and it’ll detect all your torrents

Bit of a mare to get this working – ended up with custom script in the advanced section of NPM (with my local address in bold. Worked a treat!

location / {
proxy_pass https://192.168.0.3:443/admin/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_hide_header X-Frame-Options;
proxy_set_header X-Frame-Options “SAMEORIGIN”;
proxy_read_timeout 90;
}

location /admin/ {
proxy_pass https://192.168.0.3:443/admin/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_hide_header X-Frame-Options;
proxy_set_header X-Frame-Options “SAMEORIGIN”;
proxy_read_timeout 90;
}

location /api/ {
proxy_pass https://192.168.0.3:443/api/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_hide_header X-Frame-Options;
proxy_set_header X-Frame-Options “SAMEORIGIN”;
proxy_read_timeout 90;
}

Well, wifi kept dropping out which was unusual for my Unifi setup so I had a wee look – I think tailscale has managed to screw something up. Decided to install Unifi controller onto my new UGreen NAS – what a palaver it turned out to be to get the access points adopted. Had to

login via putty to EACH access point and try and remember my credentials

set-default to reset the unit

set-inform http://myNASip:8080/inform

reboot

login to my new NAS based controller and adopt

Except 2 of the APs needed resetting to default and rebooting several times before they finally were able to get adopted. All in all it took a couple of hours. Then i realised I had done this all before on my older NAS migrating from the raspberry pi based Unifi controller……Doh!

Guess i’m just thankful I was able to do this all remotely rather than having to physically reset them…..

Unifi SSH for dummies

Bit of a learning curve – installing tailscale on my pihole and setting it up to use pihole as the dns server so i can block ads on the go from anywhere  🙂

Used the guide here https://tailscale.com/kb/1114/pi-hole and then to set it up as an exit node login via SSH use

echo ‘net.ipv4.ip_forward = 1’ | sudo tee -a /etc/sysctl.conf
echo ‘net.ipv6.conf.all.forwarding = 1’ | sudo tee -a /etc/sysctl.conf
sudo sysctl -p /etc/sysctl.conf

sudo tailscale set –advertise-exit-node

Remember to set the pihole as the DNS server for the tailnet!

To configure the Raspberry Pi as the DNS server for your tailnet, go to the DNS page of the admin console, and in the Nameservers section, select Add nameserver, then Custom. Then enter the IP address for the Raspberry Pi, select Save, and enable the Override DNS servers toggle.

Managed to completely bork everything by having pihole wipe my custom dns server address (unbound on 127.0.0.1#5335 ) Once i re-added this it works a treat. Trying to get my head round tailscale now so i can use it when on holidays to browse via my home pihole(s)