G'day all,

I am an Aussie who has just moved to the South of the UK and have been looking at the 1300 RT as an option to get out on the road for some nice long European road trips. At home in Sydney I have a number of Ducati's (Multistrada / Panigale / Scramblers) but keen to give the 1300 boxer a go.

Anyone have an RT? Love to know any concerns you have and equally things you love. I am test riding one on Friday but thought I would enlist the power of Reddit to get some thoughts before I ride the bike.

Also love to know must do rides in the UK and Europe.

Thanks legends.

Cheers,
Steve

Morning all,

My son purchased the Fishing Planet: Kaiji No Ri Weekend Escape add on via his XBox console. Got order confirmation email from Microsoft (MS) / credit card charged but add on is no where to be seen. Not shown under game -> add ons and in MS store it just shows to buy. Cleared game cache and contacted MS and Fishing planet support who just point finger at each other.

Any clues? Has happened to him a few times now with this game using his own money so got a very disappointed 13 year old here!

Cheers

Steve

Long post, grab a coffee. I spent the last two days turning my Ugreen DXP480T+ into a proper self-hosted home lab and wanted to share the full journey for anyone thinking about doing the same. This is everything I built, the problems I hit, and how I solved them.

The starting point

I had a decent setup already — ASUS ZenWiFi BQ16 router, Ugreen DXP480T+ NAS (running Docker), a headless MS-02 Ultra workstation on 10GbE, 8Gbps symmetrical broadband, and a second Ugreen DH2300 NAS for storage. I was using Quad9 as my DNS resolver and NordPass for passwords. Nothing was self-hosted beyond basic file storage.

Goal: Move as much as possible onto the NAS, keep everything encrypted, and make it all accessible from anywhere via a proper VPN — not just RDP.

Step 1 — DNS: Quad9 → AdGuard Home (local)

I started by evaluating AdGuard Private DNS cloud vs running AdGuard Home locally on the NAS. The cloud option was already paid for (lifetime sub) but local wins on privacy since DNS queries never leave your network.

The port 53 problem: UGOS ships with dnsmasq listening on 127.0.0.1:53. AdGuard Home in host network mode needs port 53. After trying various workarounds (binding to specific IPs, alternative ports), the cleanest solution was disabling dnsmasq entirely with systemctl disable dnsmasq and letting AdGuard Home own port 53 on 0.0.0.0.

Result: AdGuard Home running in Docker on the NAS, handling all DNS for the network via the BQ16 WAN DNS settings. Encrypted upstreams to Quad9 and AdGuard cloud over DNS-over-TLS. Currently blocking around 36% of all DNS queries across the network.

Blocklists running:

• AdGuard DNS filter (163k rules)
• HaGeZi Pro++ (236k rules)
• HaGeZi Ultimate (288k rules)
• OISD Big (453k rules)
• HaGeZi Windows/Office Tracking
• URLHaus Malicious URLs

Step 2 — Tailscale for remote access

Replaced RDP-over-local-network with proper zero-trust VPN. Tailscale runs as a Docker container on the NAS and:

• Advertises the 192.168.50.0/24 subnet so remote devices can reach all LAN services
• Acts as an exit node so family members travelling abroad can route all traffic through home
• DNS is configured to use AdGuard Home, so ad blocking works on every device on the Tailnet

The DNS headache: Getting Tailscale to correctly route DNS to AdGuard Home took a few iterations. The final working config:

• Two nameservers in Tailscale admin: one unrestricted pointing to NAS LAN IP, one restricted to your internal domain
• AdGuard Home listening on 0.0.0.0:53 (not just the LAN IP) so it's reachable via the Tailscale tunnel

Free plan covers up to 100 devices — perfect for a family of 6 with 12 devices.

Step 3 — Nginx Proxy Manager + SSL

The BQ16 runs its own nginx on ports 80 and 443. Fix: disable the port 80/443 redirects in UGOS Control Panel → Device Connection → Portal Settings (uncheck "Redirect port 80" and "Redirect port 443"). This frees the standard ports for NPM.

Known NPM + Ionos DNS challenge bug: When requesting Let's Encrypt certs via the Ionos DNS plugin, NPM throws an "Internal Error" / "Invalid JSON" in the UI but the certificate IS actually being issued in the background (takes ~15 mins for DNS propagation). Workaround: ignore the UI error, wait 15 mins, check docker logs nginx-proxy-manager --tail 10 for "Successfully received certificate", then add it as a standalone cert via Add Certificate → Let's Encrypt via DNS and assign it to the proxy host.

Result: All internal services accessible via clean HTTPS URLs with valid Let's Encrypt certs — no port numbers, no warnings.

Step 4 — Vaultwarden (self-hosted Bitwarden)

Migrated entirely from NordPass. Single Docker container, mounted to /volume1/docker/vaultwarden/data. Exposed via NPM with HTTPS.

NordPass export → Vaultwarden import: NordPass CSV exports cleanly. In Vaultwarden go to Tools → Import Data → select NordPass CSV. Entire vault imported in under a minute.

Bitwarden browser extension works identically to NordPass once you point it at your self-hosted server URL. Mobile app works the same. Over Tailscale it works from anywhere — the vault is cached locally so it's accessible even offline.

Step 5 — Immich (self-hosted Google Photos)

Multi-container deployment via Docker Compose:

• immich-server
• immich-machine-learning (facial recognition, CLIP search)
• postgres (using the Immich-specific postgres image with pgvector)
• redis

Currently have ~700GB used on a 3.7TB volume with plenty of room for a 1TB+ Google Photos migration.

Running at https://photos.yourdomain.com via NPM.

Step 6 — Uptime Kuma (monitoring)

Lightweight monitoring for all services. Single container. Monitoring:

• All internal HTTPS services (200 OK checks every 60 seconds, 3 retries before alerting)
• AdGuard DNS (DNS record check against 192.168.x.x)
• Telegram alerts configured for instant notification if anything goes down

Tip: For services accessed via internal DNS rewrites, use the direct IP:port in Uptime Kuma rather than the domain name, since the Kuma container resolves DNS differently inside Docker.

Step 7 — Landing page

Simple static HTML served by an nginx:alpine container on port 8080, proxied via NPM. One bookmark on every device covers all services. Dark themed, loads instantly, no JavaScript framework needed.

Full service list

Service	Tech	Purpose
AdGuard Home	Docker	DNS filtering, ad blocking
Tailscale	Docker	Zero-trust VPN, exit node
Nginx Proxy Manager	Docker	Reverse proxy, SSL termination
Vaultwarden	Docker	Password manager
Immich	Docker Compose	Photo library
Uptime Kuma	Docker	Service monitoring
Homepage	nginx:alpine	Landing page

Hardware

• NAS: Ugreen DXP480T+ (primary, all Docker workloads)
• NAS: Ugreen DH2300 (secondary, backup target — NAS-to-NAS replication planned)
• Router: ASUS ZenWiFi BQ16 (10GbE WAN, DNS pointed at NAS)
• Workstation: MS-02 Ultra running LM Studio + Ollama (headless, 10GbE)
• Network: multi-gigabit symmetrical fibre — no bottlenecks anywhere

Key lessons learned

dnsmasq vs AdGuard Home: Don't try to work around it with port workarounds. Just disable dnsmasq and let AdGuard Home own port 53.

Tailscale DNS: The phone/remote device DNS issue is almost always "AdGuard Home isn't listening on the right interface." Binding to 0.0.0.0:53 instead of a specific LAN IP fixes it.

NPM + Ionos DNS challenge: The Internal Error is a UI bug. The cert is still issued. Just wait and check the logs.

IPv6 on Windows: If a Windows machine isn't using your custom DNS despite setting it manually, it's because IPv6 DNS takes priority. Disable IPv6 on the adapter with Disable-NetAdapterBinding -ComponentID ms_tcpip6.

Port conflicts on Ugreen NAS: UGOS uses ports 80, 443, 9443, 9999, 5443. Free up 80/443 for NPM via Control Panel. Everything else can stay as-is.

Happy to answer questions on any part of this. The Ugreen DXP480T+ handles all of this with barely a blip on CPU/RAM — it's genuinely well-specced for a home lab NAS.

G'Day All,

Has anyone run adguard home on a Nas in a docker container? Would love in tips or feedback or tips. Will be running on Ugreen DXP480T Plus.

Thanks in advance and have a great weekend.

Cheers,

Steve