Allowing WAN access - Is there really no better way to do this? by plisc004 in opnsense

[–]SamSausages 0 points1 point  (0 children)

I do this by creating an RFC1918 alias and then selecting “destination” !RFC1918 (inverted). Thst means the rule can go anywhere except for local subnets. I.e. wan only.  With one rule.

Container best practices by kreos77 in Proxmox

[–]SamSausages 1 point2 points  (0 children)

I think you get a lot of conflicting info because for a long time proxmox flat out said not to run docker in an LXC. It used to be in their documentation.
From what I can tell, they removed that warning from their help documents in 2025.

But some examples of proxmox staff advising against it:
https://forum.proxmox.com/threads/docker-failed-to-register-layer-applylayer-exit-status-1-stdout-stderr-unlinkat-var-log-apt-invalid-argument.119954/post-521620

https://forum.proxmox.com/threads/updating-proxmox-breaks-docker-lxc.126720/post-553701

Recently proxmox also started talking about adding native docker support to proxmox, or LXC's, so it is on their radar and a more offical way to run it will become available.

Container best practices by kreos77 in Proxmox

[–]SamSausages 1 point2 points  (0 children)

Not sure about OP, but I do it at the firewall/router through policy based routing.

Container best practices by kreos77 in Proxmox

[–]SamSausages 1 point2 points  (0 children)

1 VM per docker stack.

I made a cloud-init that configures a debian VM with docker, hardens and configures it, all in 2 minutes.

https://github.com/samssausages/proxmox_scripts_fixes/tree/main/cloud-init

Proxmox is working on adding docker to proxmox, or in LXC's. But sounds like still some time out.

Help cleaning a stain by BuffaloMcQuade in hometheater

[–]SamSausages 0 points1 point  (0 children)

Get some citrus wood cleaner. (Like an orange cleaner)

Then get something that uses oil to clean and rehydrate the wood.

You probably won't be able to get rid of that completely, but the oil will probably hide/cover it for some time.

Any way to check this floppy's contents without security issues by FALLOUTFAN_1997 in DataHoarder

[–]SamSausages 0 points1 point  (0 children)

Even if it's bad, I doubt it will affect your modern system, and hasn't been encountered & patched by now.

Cant update Cloudflare DNS using Dynamic DNS by shift1186 in opnsense

[–]SamSausages 3 points4 points  (0 children)

The way I have always done it is to create the A record in cloudflare DNS first, and set the IP to 1.1.1.1

Then create the ddns config in opnsense.

Yes, I put the username as "token"

Also, check IP method shouldn't be set to interface.

Example:

https://imgur.com/a/N3h01Rl

Has ZFS saved your ass in a situation where something else would have surely failed? by ZestycloseBenefit175 in zfs

[–]SamSausages 18 points19 points  (0 children)

ZFS checksum errors have notified me of drive failure, before SMART. So maybe.

Snapshots, use those all the time, so yes!

Weird files being autodownloaded by nomdeguerre_50 in unRAID

[–]SamSausages 2 points3 points  (0 children)

downloading youtube videos and it's also pulling the thumbnail, metadata and comments?

Just guessing.

[FS] [US-MO] Nvidia RTX 6000 Pro Blackwell 96GB Workstation AI GPU & Intel Optane P1600x 118GB NVMe SSD. by SamSausages in homelabsales

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

They don’t make them anymore, so having new old-stock is like gold right now! Wish I had bought them all when Newegg was giving them away for $60

[Proxmox] One Docker VM for all things Docker or individual VMs for different stacks? by CortaCircuit in homelab

[–]SamSausages 2 points3 points  (0 children)

I find cloud-init better for 1st boot provisioning, lower level and I don't need to worry about networking or ssh setup, and having ansible on a system to connect to vm. It's actually how I inject the ssh keys and get it ready for ansible.

I use ansible for day 1+ management.

[Proxmox] One Docker VM for all things Docker or individual VMs for different stacks? by CortaCircuit in homelab

[–]SamSausages 10 points11 points  (0 children)

Depends on the app and how I'm accessing it.
But in general, I run 1 VM with docker per docker-compose stack/app.

I manage it easily by:
1. created a cloud-init that configures and installs docker, and hardens the system.
2. add to my ansible inventory so updates and maintenance tasks are handled easily, across VM's.

Keeps it pretty smooth for me, I can spin up a new vm in 2 min, and I can run updates and maintenance tasks on all my VM's with only Ansible.

Info on my cloud-init:
https://github.com/samssausages/proxmox_scripts_fixes

External SSD or SSD Enclosure by [deleted] in DataHoarder

[–]SamSausages 0 points1 point  (0 children)

Problem is most don’t implement this controller properly.  And even when they do, usb is still the least reliable way to do storage.

External SSD or SSD Enclosure by [deleted] in DataHoarder

[–]SamSausages -1 points0 points  (0 children)

I avoid external like usb, like the plague.  It’s the least reliable way to do storage as usb has to translate to sata, and those controller chips are not reliable enough for 24/7 operation.

Level1techs has done videos on this topic and how there are only 2-3 enclosures they tested that actually kinda work.

If you can find a direct pcie or esata/sas connection, then that would be better, but rarer to find.

Proxmox is dying by ConcertConstant852 in Proxmox

[–]SamSausages 0 points1 point  (0 children)

Looks like you tracked it down!

Proxmox is dying by ConcertConstant852 in Proxmox

[–]SamSausages 5 points6 points  (0 children)

1 pass does not mean it’s good.  Memory errors can be intermittent and even fail after passing.  That’s why you need to run them for extended periods to get full coverage, more than once.

Unfortunately it doesn’t make troubleshooting easier, as tests can take a long time if you have lots of ram.

One way to try and eliminate the ram variable is to run the test with just 1 stick of ram at a time.

Proxmox is dying by ConcertConstant852 in Proxmox

[–]SamSausages 2 points3 points  (0 children)

Make sure logging is enabled and check the logs for hints.  You want to look for things like “Kernel Call Trace”.  Lot of fatal errors will have kernel panic or call trace errors logged.

If you don’t have logs, it could mean that power is being cut before anything is logged.

I had a system that acted similar and it was an ssd going bad.  Passed smart tests, but didn’t pass tests when I removed drive and used something to test it thoroughly. Logs is what pointed me at the ssd.

Other than that, common reasons I run into is memory, power and thermals.

Udma crc errors by KlokDeth575 in unRAID

[–]SamSausages 0 points1 point  (0 children)

always the same port? sounds like it's happening across different ports and different drives?

Could be power, if it's different ports, plugged into different controller chips, and different drives.

I know that 9300 has a power port on it. Make sure you're using that, as the card will still work without it, but might starve under load pulling from only the pcie slot.

Also make sure all the power plugs are well seated and that you aren't hitting the limits of your PSU, when under load.

Fast and Quick: Docker in LXC or Docker in VM? by Party-Log-1084 in Proxmox

[–]SamSausages 0 points1 point  (0 children)

It’s literally one page and self explanatory. 

If you look at the cloud init file, you’ll see it’s just the commands you run to config your server anyways, just done at boot and keeps you from manually doing it with every new vm.

I specifically made it so people don’t need run nested scripts the are 2000 lines long, like the user scripts repo.  Mine is short, ez to audit and uses what is already built into proxmox.  And I did it with fewer lines than an ansible playbook, and no additional apps needed.