Is there a fix for this yet?  Not seeing a new release version so far for the servers I've checked, I wish this one was taken down, or at least not shown as available in DSU, etc because the bug is a major issue for us, we can't just use a hostname here, the DRAC must be available externally by IP.  ETA on fix? 

You have no idea how many times I've reset dracs over the weekend thinking certificate issues were the problem...

Seconded for an ETA on the fix ? --- some of us actually secure the dracs

Hello @Mattr81,

I've been looking in the internal documentation and I cannot see the specified date for the next iDRAC update. Normally, it takes 3 months from one update to the next. Considering the last one was in January maybe April or May will be the next release date. But this is only a personal guessing and should not be taken as definitive.

I will try to find out if there is a formal release date announced and post back here when I have more information on this.

Regards.

This is highly annoying and a security hole as it prompts people to accept security exceptions.  There should be an OOB fix for this issue to resolve ASAP.

Hi,

Apologies for the issue, the fix won't be far too long. I'll put a note in your case for visibility to engineering.

This is still not fixed, as far as I can tell, as of May 7 2021,  is there an ETA?

Is this an issue in iDrac 8 and 7  and if so, will the fix be back-ported?

Hey @Mattrophy,

Unfortunately I don't have any firmware release dates by engineering, but I have had a word from them and they are working on it. 

2.80.80.80 is worse.

Here, on an R630's iDRAC v2.80.80.80 (updated from 2.75.75.75 or 2.75.100.75) I can no longer log in using either a FQDN or short dns name, but can using IP address only.

Phil

---

@DELL-Shine K wrote:
Can you try below FW and share the result?

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=vdd4r&oscode=w12r2&productcode=poweredge-r630

---

I just made the mistake of upgrading one of my FC430 iDRACs to that firmware, and it's even worse.  The iDRAC is sending an empty response.

$ curl https://node01-idrac.XXX.XXX.XXX   
curl: (52) Empty reply from server

Hello,

The iDRAC Web Interface should accept the .exe file. This article doesn't state it, but the video shows the use of an .exe. I would use the file in Shine's link.

https://dell.to/33Dxrjc

Looks like 2.80.80.80, which claims to fix the issue, is out.  Anyone know where I can find a version that I can install through the iDRAC or CMC web UI?

---

@Dell-DylanJ wrote:

Hello,

 

The iDRAC Web Interface should accept the .exe file. This article doesn't state it, but the video shows the use of an .exe. I would use the file in Shine's link.

 

https://dell.to/33Dxrjc

---

I didn't think to try the .exe file directly.  I was able to get it to work by extracting the firmimg.d7
from the file and pointing the iDRAC at that file.

Sadly, the newest version seems to be even worse.  It doesn't redirect to the IP address, it just sends back an empty response.

You can get to the borked iDRAC by using its IP address, and then upload an older version of the drac code.