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 the manual install instructions here https://tailscale.com/download/linux/rpi

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)

123reg – bit of a mare to find out how to login my cpanel after previous hosting company moved to 123reg. turns out it is a wee bit more complicated https://account.123-reg.co.uk/products scroll down to webhosting and select manage all. Then find that nothing works. The hardcoded cpanel admin link doesn’t work as it points back to the previous hosting cpanel address…. so if you use https:// [my domain] /cpanel it works and you can then login. If you remember your user/password…… find the username from the 123reg panel …..:)

Still using sslfree.io to generate my certificates

The 123reg option to ‘verify DNS ownership’ doesn’t seem to work either…..

I end up learning how to do this every 90 days when i’ve forgotten it from the last time 🙂

//edit – i have changed 1 domain over to cloudflare nameservers so need to update from it’s dashboard when time comes to renew the SSL certificate for that domain….nothing is simple!

Having lots of fun with pihole and configuring unbound as a recursive dns server

This is the best guide i have found and used successfully Unbound install guide

This is another really useful guide for installing both pihole and unbound – Crosstalk solutions install guide for pihole and unbound

MS Synctoy – great piece of software – deprecated and not available in windows 11 but still works fine – downloaded version 2.1 x64 from majorgeeks.com and it works a treat. You do need .net framework 3.5. I find it useful for preparing drives and content for a forthcoming NAS acquisition……

This is what i used to finally sort out migrating controller from windows to raspberry pi docker

https://www.disk91.com/2023/technology/networks/install-unifi-controller-on-raspberry-pi/

It was all a bit of a mare after i tried to move the unifi controller from windows to a docker image running on rpi – could not get the access points to be seen so i could adopt them.Tried all the methods like set-inform etc to no avail. Ended up very frustrated and deleted the docker image and used another one to set it all up from scratch, including SSHing into the access points and factory resetting them. This worked ok via the guide above.

Bit of an odd one this – intermittantly RDP session seems to get stuck and I can’t login remotely and end up stuck on the ‘please wait’ screen – After some searching this useful guide from Eric on learnmicrosoft forums allows a workaround!

Windows PC – RDP Client mehtod- save the RDP connection to a “.rdp” file and edit the configuration through MS ‘Notepad’ to add a configuration line that will disable NLA login method and force Windows Login

1. Open MS RDP (Start->type “mstsc”->Enter) and type in the IP address you want to connect to
2. Click the “Options” button at the bottom and Click “Save” to save your connection as a “.rdp” file. Remember where you saved the file.
3. Click Start, type Notepad, Hit Enter
4. Click File, Open, traverse to the “.rdp” file you saved in 3 and open it.
5. Scroll to the last line and hit enter to add another line.
6. Add the following to turn of the Network Level Authentication: “enablecredsspsupport:i:0”
7. Click File, Save to save the “.rdp” file
8. Click Start, type “File Explorer”
9. Traverse to the directory which contains the “.rdp” file
10. Double Click the “.rdp” file
11. Connect, see Windows style login screen.
12. Enter your credentials and get past the “Please Wait” screen

Note: After adding this configuration line, when you double click the “.rdp” file to connect, it will connect to the Windows PC and then display the login page where you will have to manually type in the User and Password. Unfortunately, it will save the User for next time you connect but not the Password