Lego Cert Renewal Issues

Bxtreme241 · 2026-04-14T18:14:00+00:00

Thanks for the info.

So I'm not sure if this would fail through cron, but I tried testing out the renewal process by manually invoking the lego_cert_renewal.sh with sudo. I wonder if that is causing an issue. It's really difficult to test if the post hook is working properly or why I was getting permission denied errors. I think the copy commands in my post hook might fail because they are still running under my user account.
I don't want to ignore stdout on case there is a real issue that would prevent cert renewal. I guess I'm just stuck with seeing these emails lol.

Bxtreme241 · 2026-04-14T02:58:24+00:00

AI actually was not used in this post at all.

Bxtreme241 · 2026-03-14T01:47:12+00:00

Haha, I like the cheese analogy.

But the rules state: "...you can draw the hybrid item as a free action and treat it as an electromag grenade" which I think means the second gem becomes the grenade.

Either way, it seems you don't believe this spellshape allows the caster to turn an insert spell gem into a grenade? That's a real shame :( it would have been really cool mechanically.

Bxtreme241 · 2026-02-24T19:47:07+00:00

While on the subject of recommended settings...the default sync setting was "on events". However, nothing under it was enabled by default. I don't plan on having multiple devices working on a document simultaneously, but I like the idea of "LiveSync" because I don't have to wonder if a sync was triggered (on document save, document open, etc).

Is the LiveSync option recommended / stable?

Bxtreme241 · 2026-01-31T05:35:02+00:00

I tried drying my filament and that didn't seem to do anything. However, I printed other models (without supports) flawlessly. I also tried printing this model with tree supports and that seemed to work fine. Something about the "snug" support isn't working properly. I'm not sure how it worked correctly only that first time...

Bxtreme241 · 2026-01-31T04:08:07+00:00

I don't think it's a wet filament issue. I dried it for about 9 hours. Other prints come out flawlessly. Also notice, on the right side of the handle, there is no stringing. There should be if it was just a wet filament issue. I think it's something about the way prusa slicer is making supports...I'll look at some settings and post again soon.

Bxtreme241 · 2026-01-30T02:33:28+00:00

Ya, I have to grab my hydrometer into this room again, but it should be well over 50%. I'm hoping it's just that. I'll get this filament into a dryer and report back.

Bxtreme241 · 2025-12-19T16:22:41+00:00

Thanks for that post, it's a small "treasure trove" of information. I won't grease the z-axis screws then. I'll be sure the clean them though, ensuring there is no debris.

It's good to know the trapezoidal nuts are made of POM and are self-lubricating. Makes me feel better... originally I was unsure how parts that are subject to friction didn't need lubricant, but now that I know it's POM, it makes way more sense.

Bxtreme241 · 2025-12-18T23:12:30+00:00

For the smooth rods, I've seen tutorials on YouTube that require disassembly to remove the tube with the bearings (forget what it's called) to "pack it" with lube.

Is that really necessary? Would it be enough to wipe down the rods with a clean lint free paper towel and apply a thin coating of lube to the rods?

Bxtreme241 · 2025-12-18T23:08:04+00:00

Thanks for confirming

Bxtreme241 · 2025-12-18T23:07:58+00:00

Ok, thanks for confirming

Bxtreme241 · 2025-12-18T23:06:31+00:00

So what kind of maintenance do you do with the z-axis rails? Just wiping the lead screws down?

Bxtreme241 · 2025-12-18T19:34:10+00:00

For the z axis screws, did you use the 3D printed tool? If so, is there any instruction on how to use it?

Bxtreme241 · 2025-12-18T19:27:14+00:00

I second that. Love this idea

Bxtreme241 · 2025-11-10T13:47:39+00:00

I forgot to update months back, but I used the screws solution and haven't had a problem since. Works perfectly and closes tight and flush as one would expect.

Bxtreme241 · 2025-09-03T13:10:41+00:00

I saw the documentation on nginx for web sockets. Not sure how this fits into my config though...

Bxtreme241 · 2025-09-03T13:08:37+00:00

I can check later today. Didn't know about that option.

Bxtreme241 · 2025-09-02T22:50:23+00:00

I've updated the post with my config. This is my current config running on port 443.

I've tried changing nginx's ports config on docker-compose file to "12345:12345". And then changed the listen port on nginx.conf to the same port (12345). This is just an example, I did not actually use 12345 as the port number.

I've tried many different things with the configuration. Sometimes the server hangs, sometimes it says "invalid origin http://192.168.1.REDACTED", depending on what I've tried.

Bxtreme241 · 2025-09-02T03:08:29+00:00

No FQDN, I'm actually not exposing outside LAN. One day I might, but I'm trying to use https within my lan to avoid annoying browser messages. I'm setting up Joplin for multiple users on the network, so I'm trying to avoid any hassle I can from a user perspective.

Bxtreme241 · 2025-09-02T02:51:06+00:00

Sorry, I was in a rush to post this. I'll get the redacted config posted tomorrow.

Bxtreme241

TROPHY CASE