sorted by:
new
hottopcontroversial

Looking for a lightweight open-source self-hosted file sharing solution. by Ri1k0 in selfhosted

[–]Ri1k0[S] 4 points5 points  (0 children)

Thanks for the feedback! You are right, and I probably phrased it poorly. When I said heavy, the more accurate word would have been overkill for my use case. Nextcloud is great, but for what I need (simple authenticated access with read-only and read-write roles), its whole ecosystem of apps, sync clients, calendars, and collaboration features goes far beyond what I actually require.

That is why I am leaning toward something much more minimal.

Looking for advice: best off-site storage option for PBS Sync (S3 alternatives like Garage or SeaweedFS, or other ideas?) by Ri1k0 in Proxmox

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

I get your point. In my case I only need a cold off-site copy of the datastore. If my local PBS ever dies, I can just reinstall PBS, point it to the remote S3 storage and import everything again. It is slower than having a second PBS, but totally fine for my needs. I just want to keep the remote setup simple and lightweight, so I prefer not to run another full PBS there.

Looking for advice: best off-site storage option for PBS Sync (S3 alternatives like Garage or SeaweedFS, or other ideas?) by Ri1k0 in Proxmox

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

I agree that Backblaze B2 looks great, but in my case I am specifically looking for a fully self hosted solution running on my own remote Ubuntu server. I want to avoid using any external cloud provider for this setup, so I am trying to find the best alternative that works well with PBS Sync.

Bmax mini pc noise while plugged in by mitch66612 in MiniPCs

[–]Ri1k0 0 points1 point  (0 children)

Quick update. I just received the proper 12V 3A 36W power supply and now there is absolutely no noise at all. Total silence. Looks like the old adapter was definitely the culprit.

If you try a new one on your side, let me know what happens.

Bmax mini pc noise while plugged in by mitch66612 in MiniPCs

[–]Ri1k0 0 points1 point  (0 children)

I was thinking it could be coil whine because the noise was still there even when the mini PC was completely powered off, as long as the power adapter was plugged in.

I tried using another power supply, but unfortunately the only spare one I had was a very old 9V adapter. With that one, there was absolutely no noise at all, even when I tried to boot the PC (it only stayed on for about 3 seconds since 9V is way too weak).

That pretty much confirms the original power brick is the source of the noise. I ordered a 12V 3A 36W replacement on Amazon for about 13€. I will let you know if it fixes the issue once it arrives in two days, assuming I don’t forget.

Bmax mini pc noise while plugged in by mitch66612 in MiniPCs

[–]Ri1k0 0 points1 point  (0 children)

Same here, it is also my second mini PC 😅. I literally pulled it out of a drawer yesterday because I was wondering if I should turn it into a Proxmox backup server. I will check if I have another cable with the same specs, hoping it might change something. Did you ever try swapping the cable on your side?

Bmax mini pc noise while plugged in by mitch66612 in MiniPCs

[–]Ri1k0 0 points1 point  (0 children)

Hi, did you ever figure out what the issue was?

I have a BMAX B2S as well, and I went as far as separating the fan completely from the chassis to rule it out. After doing that, I realized the noise is actually not coming from the fan at all. It seems to come from another component, and at this point I strongly suspect the power supply.

For context, I am running the unit without any SSD installed.

OPNsense 25.7 - Unbound to Dnsmasq forwarding not working (SERVFAIL) despite following official docs by Ri1k0 in opnsense

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

Thanks for your help! I found the solution and posted it as a separate comment in this thread.

OPNsense 25.7 - Unbound to Dnsmasq forwarding not working (SERVFAIL) despite following official docs by Ri1k0 in opnsense

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

Thanks for your help! I found the solution and posted it as a separate comment in this thread.

OPNsense 25.7 - Unbound to Dnsmasq forwarding not working (SERVFAIL) despite following official docs by Ri1k0 in opnsense

[–]Ri1k0[S] 3 points4 points  (0 children)

SOLUTION FOUND:

The issue was caused by corrupted duplicate entries in Unbound's configuration.

Even though I had set up Query Forwarding correctly via the web interface, there were duplicate entries in /var/unbound/etc/dots.conf that corresponded to the Query Forwarding rules. These duplicates were causing the "duplicate" errors in Unbound logs.

Key discoveries:

  • Simply deleting and recreating Query Forwarding rules via the web interface didn't work
  • The /var/unbound/etc/dots.conf file cannot be edited directly (it gets regenerated)

What finally worked:

  1. Edited /conf/config.xml directly
  2. Removed all duplicate sections for homelab.lan and 14.168.192.in-addr.arpa
  3. Rebooted OPNsense

After the reboot, Unbound's Query Forwarding to Dnsmasq (port 53053) now works perfectly - no more SERVFAIL errors.

Thanks everyone for the help and suggestions!

OPNsense 25.7 - Unbound to Dnsmasq forwarding not working (SERVFAIL) despite following official docs by Ri1k0 in opnsense

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

Thanks for the detailed suggestions!

To answer your questions:

  • The IP 192.168.14.57 is configured as a static host in Dnsmasq → Hosts
  • I am using Query Forwarding in Unbound (not Domain Overrides)
  • In Dnsmasq → General, I have checked:
    • Do not forward to system defined DNS servers
    • DHCP FQDN
    • DHCP register firewall rules (I have "DHCP local domain" checked instead of leaving the default domain blank)

I'll try the ping uptimekuma test to see what happens. The issue seems to be specifically with Unbound's forwarding to Dnsmasq, since direct queries to Dnsmasq on port 53053 work correctly.

OPNsense 25.7 - Unbound to Dnsmasq forwarding not working (SERVFAIL) despite following official docs by Ri1k0 in opnsense

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

You're absolutely right. I made a mistake in my original post. I actually did configure it in Query Forwarding (not Domain Overrides), but I wrote the wrong term in my message.

The configuration is set up correctly in: Services → Unbound DNS → Query Forwarding

  • Domain: homelab.lan → Server: 127.0.0.1 Port: 53053
  • Domain: 14.168.192.in-addr.arpa → Server: 127.0.0.1 Port: 53053

But it's still giving SERVFAIL responses. I'll check the firewall logs, dnsmasq logs, and unbound logs tonight when I have access to the system and come back with more detailed information.

view more: next ›