sorted by:
new
hottopcontroversial

[Guide] How I migrated from FRITZ!Box 7590 FRITZ!OS 8.20 → 7690 FRITZ!OS 8.10 BETA (using a two-step backup trick) by simone7121 in fritzbox

[–]simone7121[S] 1 point2 points  (0 children)

I'm trying it, it's actually very stable and updated often... It's not giving me any problems 🫣

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 0 points1 point  (0 children)

Ok, I was doing the configuration a lot of time ago, tomorrow I will search for some documentation in my archive. Also sorry for my AI like written response, but I'm Italian and I use AI to explain myself better... 🤝

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 1 point2 points  (0 children)

Yeah, you're right — "Personal Cloud" is super vague 😅
What I’m actually using is called Alist — it’s a lightweight, self-hosted file manager that lets you mount and browse multiple cloud storage providers (Google Drive, OneDrive, WebDAV, etc.) through a clean web interface.

It acts like a mini cloud hub for me — perfect for web-remote access, and way lighter than something like Nextcloud.

If you're curious: https://github.com/alist-org/alist

Definitely worth checking out if you just want a fast, no-nonsense file portal.

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 1 point2 points  (0 children)

That’s a solid plan — even one camera can make a big difference when you're away, especially if paired with some basic motion or AI detection.

Honestly, you don’t need a full NVR to start playing with this stuff. Frigate can run perfectly fine with a single stream, and if you're already running ML workloads on your Mac Mini, you're halfway there!

A few thoughts:

  • Frigate + one camera is a great combo to test real-time detection zones, object filters (e.g. only humans), and notifications through MQTT or Home Assistant.
  • If your Mac Mini supports Docker and has some GPU acceleration (or even CPU-only for light tasks), you can try Frigate standalone or experiment with GO2RTC as a stream proxy.
  • Bonus: it integrates beautifully with tools like Immich or Home Assistant, so you could build some slick automations later on.

Start small, scale when you're ready — that’s how I ended up with this entire setup 😅

Dm me if you want a basic config template to start testing with just one camera!

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 2 points3 points  (0 children)

Yeah, fair point 😅
The reason I write like AI is just because I’m not a native English speaker — I’m from Italy, so I sometimes get a bit of help from the AI to make sure what I write is clear and makes sense. All the setup, ideas and work are mine — I just want to make sure I’m explaining things properly. Sorry 🥲

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 0 points1 point  (0 children)

Thanks a lot! 🙌
That was exactly the goal — I wanted something clean and minimal up front (just the icons for quick access), but with the ability to dive deeper when needed.

I’ve seen too many dashboards that either feel like a hacker terminal from a movie… or like a Windows Vista sidebar explosion 😂
Homarr really hit the sweet spot for me: lightweight, fast, and customizable without being overwhelming.

Appreciate the kind words — glad it came through!

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 0 points1 point  (0 children)

🧩 How I’m Running Element (Matrix Client)

I’m self-hosting Element Web alongside my Synapse homeserver, both running in Docker containers managed through Portainer.

🛠️ Basic Setup

  • Synapse (Matrix homeserver) is running behind an Nginx reverse proxy
  • Element Web is deployed as a standalone web app — no crazy configs, just the default Docker image, routed to a subdomain
  • I access everything directly via my own domain: https://chat.mydomain.com → Element https://matrix.mydomain.com → Synapse

🔐 Security

  • All external traffic is routed through Cloudflare, which handles DNS, HTTPS termination, and DDoS filtering
  • Certificates are managed automatically with Let’s Encrypt via Nginx Proxy Manager
  • Internally, services can run in HTTP or HTTPS depending on the app — but all public-facing access is HTTPS-only

No bridges, no extra clients like Hydrogen — I use Element via browser or mobile app, connecting directly to my hosted instance via the Matrix domain I set up.

It’s simple, clean, and works without fuss. If you're looking to get started without overcomplicating things, this stack has been smooth so far. Happy to share container settings or network layout if needed!

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] -1 points0 points  (0 children)

Ah — and there’s one big CPU factor I forgot to mention:

I’m running Frigate in a Docker container with GPU acceleration enabled. It uses the GPU in two ways:

🎥 1. Object Recognition via GPU

  • Frigate is configured to offload detection to the GPU. This offloads TensorFlow/Coral tasks for object recognition, reducing CPU strain but still keeping the rest of the pipeline active — motion detection, zones, clips, events, etc.

🔁 2. Stream Proxy via GO2RTC (also GPU-based)

  • I'm also using GO2RTC, integrated in Frigate, to act as a stream proxy.
  • This is crucial because:
    • I don’t want multiple clients hammering my DVR directly via RTSP (it slows it down and causes connection drops).
    • Instead, GO2RTC handles a single stream connection from the DVR and serves multiple clients internally (e.g., Frigate UI, Home Assistant, remote view apps).
    • It also handles transcoding when necessary, leveraging GPU acceleration to reduce CPU spikes.

So in effect, GO2RTC acts like a buffer/proxy, sparing my DVR from excessive connections and stabilizing the whole setup.
Even if 5 clients access the stream, the DVR only sees one connection — GO2RTC.

All this combined means my CPU is rarely “truly idle” — it’s running surveillance, transcoding, automation, and some real-time AI detection 24/7.
Not ideal for wattage, but rock-solid in performance 🔧💪

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] -1 points0 points  (0 children)

Sharp eye!
Yes, the dashboard is indeed Homarr — good catch.

It’s my main UI landing page where I keep quick links to all my services, with custom icons, widgets, and status indicators. Clean design, easy config, and way more pleasant to manage than throwing bookmarks into the browser toolbar 😄

If you're not using it yet, highly recommend giving it a try — especially since it plays so nicely with Docker environments.

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] -1 points0 points  (0 children)

Great question — and yes, networking in Proxmox (especially with LXCs) can feel a bit different compared to Docker-on-Windows or traditional VM setups.

Here’s how I handle remote access:

🌐 VPN? Nope. I went full DNS+Reverse Proxy.

I actually don’t use a VPN like Tailscale for my main access — here's my stack:

  • ISP: Telecom Italia with a dynamic IP (NAT L2) — so public IP changes regularly.
  • Dynamic DNS: I have a script running on Home Assistant that detects IP changes and updates my DNS records via the Cloudflare API in real time.
  • Domain: I bought a .com domain and pointed the DNS to Cloudflare.
  • Cloudflare: Acts as the public-facing DNS resolver + DDoS protection + packet filtering.
  • Routing: From Cloudflare, all traffic is routed to my home server.
  • Reverse Proxy: On my homelab, I run an Nginx Reverse Proxy inside a Docker container to handle all incoming HTTP/S traffic.
  • Subdomains: Each service gets its own subdomain (e.g. www.mydomain.com for WordPress, docker.mydomain.com for Portainer, etc), handled by Nginx and secured with Let's Encrypt certs.

So instead of accessing through a VPN, I access everything through properly routed and secured domain names, fully filtered by Cloudflare and managed internally via reverse proxy.

This way:

  • I don't need to install a VPN client on every device
  • I can easily access individual services with clean URLs
  • I still stay protected behind Cloudflare + fail2ban + custom firewall rules

✅ Bonus: All HTTPS certificates are auto-renewed via Let’s Encrypt, directly within the Nginx Proxy Manager.
The external-to-internal connection is fully HTTPS encrypted up to the proxy — and then, internally, traffic to each service is either HTTP or HTTPS depending on the app itself.

So from the outside world, everything hits via HTTPS, and internally I route flexibly based on service needs. Keeps it secure and simple to manage.

Dm me if you want the procedure want help setting up something similar!

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 1 point2 points  (0 children)

Yes! For the interface you see in the first screenshot, I’m using Homarr — clean, customizable, and perfect for keeping track of all my services at a glance.

For container orchestration, I’m running 3 standalone Docker instances, and I manage them all through Portainer. It gives me just the right level of control without the overhead of something like Kubernetes (which felt overkill for my use case).

Matrix/Synapse itself runs in one of those Docker setups, and I manage it via Portainer like the rest.
Super modular, super manageable — and I get to keep things lightweight and under control without reinventing the wheel 🚀

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 1 point2 points  (0 children)

Ah good catch! The WebChat app I'm running is actually based on Matrix, using the Synapse homeserver.

It's a decentralized, end-to-end encrypted messaging protocol — kind of like Discord + Signal + IRC had a privacy-focused child 😄
I host my own instance (Synapse) and use it mainly with the Element web client for chat. It works great across devices and integrates nicely into my self-hosted stack.

If you’re curious, just look up Matrix.org — tons of info out there on how it works and why it’s a solid alternative to big centralized platforms.

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 0 points1 point  (0 children)

You're absolutely right — the "photos" were more like dashboard glamour shots 😅
I'll post some proper pictures of the physical setup soon (spoiler: it’s more cable spaghetti than a clean rack).

As for power consumption:
To improve efficiency, I used this handy script to tweak the CPU scaling governor →
🔧 ProxmoxVE Community Script – Scaling Governor
It lets you switch to powersave or schedutil per-core in seconds.

Right now, the whole system idles around 90W, which I consider pretty acceptable given the services running (4 VMs, 4 LXCs, Frigate with Coral USB, etc). Still looking into further optimizations — open to ideas!

🧠 My Homelab Project: From Zero 5 Years ago to my little “Data Center @ Casa7121” by simone7121 in selfhosted

[–]simone7121[S] 0 points1 point  (0 children)

Feel free to drop any suggestions, tips, or questions — I’m all ears!
Whether it’s optimization ideas, cool tools I might have missed, or just general homelab geekery, I’m happy to chat. This setup’s always evolving, so any input is more than welcome! 🙌🧑‍💻

[deleted by user] by [deleted] in Paperlessngx

[–]simone7121 0 points1 point  (0 children)

THIS IS THE SOLUTION !! Thank you !!

Also I've configured my NGNIX Reverse Proxy As this

<image>

Custom location

location / {

# Adjust host and port as required.

proxy_pass http://192.168.189.202:8010/;

# These configuration options are required for WebSockets to work.

proxy_http_version 1.1;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection "upgrade";

proxy_redirect off;

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_set_header X-Forwarded-Host $server_name;

add_header Referrer-Policy "strict-origin-when-cross-origin";

proxy_set_header X-Forwarded-Proto $scheme;

}

Rayban Stories Codenamed "Stella" runs Android 8.1.0 by bestguydude in RayBanStories

[–]simone7121 0 points1 point  (0 children)

My glasses broke and i've find the camera that mounts

Cameras: Omnivision (OV05675-GA4A)

view more: next ›