Unable to complete enrollment portal

[paranoidi]

No matter what I try I always get stuck with this screen after clicking continue in "Set up your device to get access" screen.

... while using the said application. Well done microslop.

I had exactly same issue when trying to run it natively on Mint Cinnamon.

Any ideas would be greatly appreciated.

[nathancartlidge]

I also had this issue on v0.16.0 on Fedora 42, however v0.15.0 worked correctly.

[paranoidi]

@nathancartlidge That is excellent insight. I did try downgrading intuneme to v0.15 but the issue persist.

Possibly because the intuneme init will still fetch latest image.
Pulling and extracting OCI image ghcr.io/frostyard/ubuntu-intune:latest (via podman)...

I logged into the container shell and this is the portal version:

$ intune-portal -V
intune-portal 1.2603.31

I also tried various different versions of intune-portal in my host machine, no luck so far.

[bketelsen]

@nathancartlidge what's the intune-portal version in your working container?

[nathancartlidge]

Inside the container:

$ intune-portal --version
intune-portal 1.2511.11

Outside the container:

$ intuneme --version
intuneme version 0.15.0 (Commit: 7824e482be4a89b6517d7989c1f9e157025e0de5) (Date: 2026-03-19T16:26:08Z) (Built by: goreleaser)

I didn't do any particular setup to change which image was fetched during init

[erenoglu]

hitting the same issue. No specific errors on the console. This is happening after successful authentication.

[paranoidi]

I tried enrolling on a complete clean Ubuntu installation and it still failed with the same dialog. However it started to work mysteriously after I did two things:

• Logged into company confluence via my phone
• Increase my local user password complexity

I think most plausible explanation is that my account was in a somehow corrupted state that the confluence login resolved somehow.

[erenoglu]

I think this may have to do with the "Device identifier" string "not identified".

[onehalf3570]

Same problem when running under host Ubuntu 24.04 (where, without a container, intune works). Just the 'Get the app' button (that window's screen goes blank in intune if it is pressed).

Error code: 501271 (which is very informative)

I wanted to run intune-portal under strace in a container, but it's not present there and apt install fails - is it supposed to work from the container?
Any other tips on how to debug this perhaps?
Thanks.

UPD: I don't know what changed, but after a host (Ubuntu) restart, the process continues (it still bumps into #155, but that's a different issue). UPD2: perhaps ms-edge should be started in the container first, before intune-portal