Hi, I’m awaiting more support from a Tier 2 Tech from Autodesk but I thought I would ask the forum if anyone else has had this issue.
When I went to open flame yesterday, I got an error that there was no internet connection so I couldn’t login using my single-user login. However, my network hasn’t changed and all other apps can reach the internet no problem.
I used the AdskLicensingSupportTool with --checkurls and it was able to reach all the required URLs without a problem.
I installed the latest AdskLicensing Client 12.1.0.7121 and I actually reinstalled Flame as well with no luck. I also tried changing my DNS to 8.8.8.8 as well.
If anyone has seen this or has any other suggestions while I await more support from Autodesk I would love to try them.
Edit: Forgot to mention I’m on Rocky Linux Flame 23.0.1
Yea I would have expected something like that 30 days or at least 10 days but who knows. Still awaiting Tier 2 support for this issue. its very strange…I’m tempted to reinstall Rocky Linux from scratch but I had a few little tricky issues when I first installed it that I got past (with help from the logik community!) that I don’t want to have to deal with again if possible. Luckily I’m not in a bind right now with projects in Flame due this week but I would like to get this solved ASAP.
Hey Yann, yes i did reset my license. before i reset it I was getting a different page that just said “connect to internet”. Still the same result though.
Unfortunately having the same issue… I had two days left to establish a connection so I tried reinstalling the software and resetting my license. Now I still have no internet connection and still cannot log on.
Running the License Support Tool shows no issue with connections, although I cannot ping autodesk.com from terminal…
Unfortunately I never figured it out. Ended up with a full Linux reinstall. I know of another person that ran into this problem too and they did the same thing. I did not do a full discovery with autodesk to see if they could fix it. One thing I know I had in common with the other person that it happened to was that we use lucid link but no idea if that was part of the issue or not.
Sorry, I wish you luck figuring it out. Please let me know if you do. If I can help in some way let me know.
The error message seems to indicate a DNS lookup error for one or another reason. Some causes can be VPN connections.
Either way, one possible short-term fix might be to look up the IP addresses in question elsewhere and manually add them to the /etc/hosts file. That’s should always work as an override to any dynamic lookup that doesn’t work.
Of course you run the risk that if the IP addresses changes or is load balanced, that your solution won’t keep up with that.
I have been working on this issue for close to two years with Autodesk.
Unfortunately licensing is totally separate from Flame support/development and it’s an Autodesk wide team with few people that have a Linux background. After all this time, it seems we’ve finally got traction with the licensing developers now. Over the past few weeks we’ve tried resetting certificates and several other potential fixes - and while they thought they were finally able to repro the issue internally and had a workaround - as of yet we still don’t have a solution that works for me.
So I believe that currently the only known solve is a reinstall of the OS - which is obviously not really practical, especially if you’ve got hours of material that has to be archived and restored.
The good news is I’m scheduled for a TV with the licensing team to look into the issue the beginning of next week. This is the first time I’ve had direct contact with this team and the first time they’ll be hands on with the problem. Till now they’ve be looking at logs and working internally on it. So I’m hopeful that they are all in to finally figure the cause of this out as quickly as possible.
I can keep you posted with any progress that I’m made aware of. But for now I’d file a case with support ASAP and see how they can help. The more it’s reported and the more they see this is a bigger problem, the more likely they are to divert sources to solving it.
Plot thickens. Second Flame which was working without issue now has the same problem. No updates, no new software, no changes… just woke up and chose violence.
…and thank you for all of this info and background. I really appreciate it and all that you’ve been dealing with this past few years. Please keep me posted. Luckily everything is archived off the two machines in question but Jesus… this is bananas.
I don’t know guys… We keep MPAA/TPN certified security measures. Meaning our production network is pretty cut off from the rest of the world apart from ShitGrid and ADSK Licensing, and never had this issue.
If you have a restrictive firewall, I’d make sure you aren’t Whitelisting IPs, since ADSK uses AWS for backend, and those service could be bouncing between different servers.
