@marcosm said in pf-sense-api-client: Are you trying to update it using the index number? If so, try using the name; aliases are now identified by their name rather than the index number. Yes, I was updating it using its ID number. If I change the ID to the name, I still get the same error. 2025-09-04 16:13:23.000000-04:00 pfnet-controller 2646 WARNING 43643 [x.x.x.x:34302] POST /api/aliases/TEST_API (DONE 1.378ms) ERROR: name missing 2025-09-04 16:13:23.000000-04:00 pfnet-controller 2646 Updating alias name: , ID: 25... 2025-09-04 16:13:23.000000-04:00 pfnet-controller 2646 > {"alias": {"name": "TEST_API"}, "id": "TEST_API"}

@tkerr It is much better to download the raw file. I apologize for my ignorance.

It's normally not recommended but it should be fine for a quick edit. IIRC it's under the system tree - it will be obvious since it's a long base64 string.

Hmm, I'll dig further...

I got hit with this foot gun today also. Might be a long day but the registration process confused me. So, no need to activate the controller "to itself" ?

You're right, that will work on the upcoming pfSense+ 25.07 release.

@pfGeorge good, thank you

There isn't any specific handling in MIM for HA setups yet. It's something we expect to have though. It's exactly the sort of thing I'd want to see there.

@keyser Kind of strange that Netgate keeps the cards so close on this product… I would think the point of MIM is to attract more customers to pfSense (and keep current customers aboard that might be looking for alternatives because of the “missing” MIM). Why not just answer the 4 questions so we all know what to expect and can plan accordingly? It’s hardly “subject to changes” or “undiscovered territory” type of questions. They must have debated those points LOTS of times before the product became an actual reality like its starting to become now.

Ah, that would do it! Explains why I couldn't replicate it.

@stephenw10 said in request handler failed: Great feedback. Thanks! Yeah I have some configs with deliberately huge aliases and it gets....interesting! Pleasure. I think the biggest problem that results in no aliases/rules shown will be the empty descriptions that are/were allowed in the past, many configs will spout them,

@stephenw10 If you need more info, fire away as I'm in prep mode for next week for a workshop with new pfsense features and stuff, so anything I can get to you to get fixed for 24.11 release or afterwards would nice as I can show it and tell people "it's getting fixed as we speak" :)

@stephenw10 said in [Howto] reset MIM: It shouldn't actually cause any issues though. It was constantly using an existing WireGuard-tunnel for this, I didn't like that. Spoiler [image: 1731419589339-screenshot-2024-11-12-145236.png]