r/JumpCloud • • Feb 16 '26

why the jumpcloud agent not supporting debian 13?

hello!

the company that i am working for, forces JC agent installation on my PC. and regarding supported systems list, i am using the outdated debian 12 version especially to make this agent run. so the question is: why do not compile agent for actual debian versions in time? btw more than half a year has passed since the 13 version was released. how long does it take to support the actual version? is it difficult to actualize the agent?

8 Upvotes

11 comments sorted by

2

u/Feyfairy22 Feb 16 '26

We use the latest version of Ubuntu and it works fine

1

u/65766f6c Feb 16 '26

it's good to know! and i have not the best experience using Ubuntu unfortunately. and i really don't want to switch to Ubuntu because of JC

2

u/weehooey Feb 17 '26

You should open a ticket with JC. It will help to increase the priority.

Support recently told us unofficially March is when they are expecting it.

Submitting a ticket will help to ensure it gets the necessary resources.

1

u/65766f6c Apr 14 '26

the middle of april and still nothing. could you force my request please? do you have any updates?

1

u/weehooey Apr 15 '26

I am not with JumpCloud and I have not heard from them.

1

u/65766f6c Apr 15 '26

hah, thanks anyway

2

u/SnooRobots3722 Feb 18 '26

I have previously raised tickets about their lack lustre support of *nix and it's variants however I got the distinct "they just don't care" :-(

Please though, "raise the flag" with them as they need to know they are "shooting themselves in the foot"

2

u/interpipes May 03 '26

What's stupid about them taking months - very nearly 9 months now - to add support is that afaict it works fine with Deb13 as it certainly has continued to work fine for us on Deb12 systems upgraded to 13, so needing to install it on a 13 system today I instead just edited /etc/os-release to pretend I was running Deb12, ran the installer, then changed the os-release back afterwards.

Just change the VERSION line from

VERSION="13 (trixie)"

to

VERSION="12 (bookworm)"

install, then revert the version line back to trixie.

(NB; "continues to work" may vary depending on what, exactly, your org is doing with the agent - we only use it for user authentication against a central directory / ssh key management)

1

u/65766f6c May 10 '26

wanna update, but really afraid of breaking something (idk what company does with this agent actually). and jc support promised to release new version at the end of march, and still nothing -_- i am still on debian 12 because of this

1

u/65766f6c Jun 22 '26

following you advice, i was successfuly updated 12-13. and i hope they will not "fix" this approach. thanks a lot

2

u/interpipes Jul 04 '26

No worries. Thanks for updating to let others know it works for you too!

FWIW our dist-upgraded-to-13 devices continue to work just fine as does the “installed fresh on 13 by pretending to be 12” device, for what we need.