To add some more info to what the others are saying, if your public IP address is in the range 100.64.0.0/10 (so between 100.64.0.0 and 100.127.255.255) then it is a CGNAT IP and you will not be able to make port forwarding/NAT work to/from the public internet because your public IP is not actually a publicly routable IP on the internet no matter what your ISP calls it. Hope that helps!

I had a few ideas, I’m suspicious that handbrake is falling back to CPU, maybe check the logs of the container to make sure it isn’t falling back to CPU decoding. Otherwise here are a few things I would check next:

• If you are not using docker locally so you are already doing this, you will need to configure the docker container to pass through the GPU for quicksync to work inside the container.
• If you are already doing that then I would make sure the device is the same name on the synology, it probably is but just to be sure.
• you will likely need to add your user to the video and/or render group on the synology if you haven’t, especially if you are running the container as your user instead of root
• make sure you are reading and writing to volumes that use bind mounts and not docker volumes, overlayfs is not what I would call fast and writing especially.

So I had a few thoughts. I’m not sure that you can use the docker device flag with a directory as you have there, I think it expects a device node, you can pass that directory as a volume (-v) though.

If that doesn’t work you might also try running the VM with host-passthrough mode set on the CPU as well if it isn’t set that way already, sometimes that is also required for pass through to work from my experience. Also, make sure you passed through the whole device node, sometimes there are audio devices you have to pass through with the GPU device or you will get odd errors like those initialization ones you had. I’m not sure if this is the case for Intel iGPU though offhand though. Are you able to use intel_gpu_top on the VM to access the GPU? None of that is necessarily specific to proxmox though (but probably applies to anything libvirt powered) so YMMV.

Edit: I realized you may not know what a “device node” is, that is the full path to the device, like /dev/dri/renderD128 vs /dev/dri which is actually a directory.

I do on some of mine because it makes some of the automation i have for them simpler to maintain when it is also applied to x86 hardware or virtual machines. It used to be a huge pain to use on a pi but it works pretty well these days, especially since about 24.04 I want to say.

All of the advice here is great but that is a Bambu printer, you should run its calibration routine again I would say and see what it says it also should be able to compensate if the bed is warped if you tell it to do bed leveling (unless the A1 doesn’t do that, I think it does though).

Also, when you say collisions is the printer colliding with itself or the part? You can also run an homing routine and manually move the hotend around to see if it has issues.

Also RE the local event, is the air temp really hot where you are? You might need extra part and hotend cooling if the ambient temp is like 40C or something. I mean like tweak the slicer not put an external fan on it necessarily hah.

It’s funny you say that, I have one of those but he actively demands that I turn the water on so he can drink from it hah!

He definitely has enough water bowls around including directly next to that sink, he has done that since he was a kitten. No idea why, I just work here :D

In case anyone here doesn’t follow it, Ivan’s YouTube channel is awesome, he has been working on a crazy marble clock: https://youtu.be/K3FMVmAte3g

ProperPrinting is also great, he has some cool videos on custom extruders and printers he designed and a wild extruding resin printer with UV lasers.

Oh it is certainly not just you, I am sometimes confused reading them even for commands I have used for years and I know what flag I am looking for but don’t remember the exact syntax or something hah! I am glad they are there but they are definitely not a complete guide to any command, especially built-ins.

Interestingly, this is something AI has been very useful for to me, less searching because I can describe the outcome I want and it figures out what I am talking about generally.

Okay so the disks aren’t also on UPS? That might actually be even worse than the whole thing getting turned off, ZFS is definitely not meant to be run on removable disks like that.

Okay so when you say “unplug the power” do you mean shut it down first or just pull the plug? The latter is a great way to corrupt your storage pools as ZFS uses memory for read and write cache etc by default. You definitely need to do a graceful shutdown especially if there is data that was recently written to disk, that’s why a UPS is so recommended. That said you can usually import an existing pool when that happens, I think there is a UI menu for it now.

As others have said, be careful with fans if they are large, many of the plugs don’t have a very high wattage rating and are all definitely rated for 15a at max usually, you might consider a smart relay instead (like a Shelly or something).

That said I have switches and plug-in and in-wall relays from Aqara (zigbee) and TP-Link (WiFi) and zooz (zwave) and all are fine and do the job. Not all support power monitoring if that is something that matters to you, it’s not a universal feature.

Have you tried adding 239.255.255.250/32 to your outbound subnets variable? This is the multicast address for SSDP which mDNS ultimately relies on if I remember right, I recall having to do this for Plex in the past.

In addition to what others have said there is an interesting video from Veratasium about that NIST department, they have a wild variety of items.

Just to make sure, all of your links need to be in quotes if they are not. The : in a url can make some yaml parsers think that it is another block, there are other URL safe characters in general that are special characters in yaml so it’s a good idea to put them in quotes.

In addition to everyone’s suggestions, have you tried rotating the part so it is at a 45 on the bed? This will keep the printer from accelerating as much in the Y direction since it is not a straight motion, I used to have to do that for tall prints on my Mk3 sometimes.

Also, if I were printing that part I would flip it over unless there is some reason you can’t. You might also get more rigidity using normal supports for the large surface facing the bed, might print faster too, tree supports for large areas take a while for me usually.

I am so glad you keep posting, your builds are beautiful and are an inspiration to me to make my builds look good so keep it up :D. I really like the roof on this one, might have to copy that for one of my factories.

I don’t have anything to add but I am glad someone posts this every week, I always find something new, so please keep it up :D

Shout out to Everything Smart Home, great YouTube channel as well!

Just to add my 2c, I just started using this the other day just as an quick UI for ollama and I was blown away at how many features it has and i think the interface is well done. It’s really a great tool so far and I’ll definitely be using it more going forward!

I know you solved it but for anyone that finds this later this feature/behavior is typically called “NAT Hairpin” in case you are looking for a setting to enable or disable, hope this helps!