It’s not a clean Linux install at all. I’ve had 2024 & 2025 on this system.
@AdamArcher - I kind of, sort of, like my installs a little bit dirty… 
1 Like
Yeh exactly, this is what I mentioned above. It doesnt give problems when you already had early version cause you were already logged in with previous licensing so the login detailes credentials and certificates data are already stored. If you go clean you’ll face this issue.
Not throwing shit, man, just clarifiying.
So as a “workaround” (i dont even think this is a workaround) install 2024.x.x first - login - then jump to 2025.x.x
1 Like
Sorry, I missed that earlier in thread. Has it been confirmed by others having this issue that they are all clean installs of Rocky they are running on?
The problem seems to be more specific to 2025.1.
I’ve installed 2025 clean sometime in June and have no problems.
Or just install 2025.1
remove all licensing componenets
dnf -y remove adskflexnetclient* adsklicensing* adskidentitymanager*
and install the ones from 2025
dnf install -C -y "$ENGINEERING"/software/adsk/flame/licensing/AdskIdentityManager/*.rpm /vol/engineering/software/adsk/flame/licensing/Licensing/*.rpm
3 Likes
if we “Sign Out”, we experience the same behavior as if it was a clean install.