Solved!
Go to SolutioniDRAC8 2.80.80.80 inaccessible using FQDN
I just upgraded iDRAC8 in four PE M630p blades of our VRTX to 2.80.80.80 and can't connect to their Web UI anymore using FQDNs I have registered for them in our DNS - browsers and curl report that server returned empty reply, though TLS handshake completes. But I can access them via the CMC by clicking on "Launch iDRAC GUI" button, which redirects to iDRAC's IP address rather than FQDN. Surprisingly, if I access GUI using https://ip.ad.dr.es they work, but not if I use the FQDN, which resolves to this same IP address.
Release notes for 2.80.80.80 state that one of the fixes is, quote, "Fixed an issue launching iDRAC Web UI from FQDN.". I'd say it broke this functionality instead since I was able to access iDRAC Web UI using either IP or FQDN before this release without any issues. Is there any way to get this fixed any time soon?
Thanks in advance for looking into this.
After upgrading to 2.80.80.80, the web UI appears completely unavailable.
The last release, 2.75.100.75 retroactively added a "Fixed CVE-2021-21510" item to the release notes, which concerned the redirections from http://hostname/ to another URL.
DELL-Charles R
Moderator
•
4730 Posts
•
25476 Points
5520
0
Posted May 14th, 2021 13:00
Hello,
I’m sorry to see DRAC is inaccessible using FQDN after the firmware update.
Try reset the DRAC from the GUI or command line: racadm racreset
Then retry.
Please let me know how it goes.
DELL-Charles R
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Accept as Solution’. ‘Thumbs up’ the posts you like!DELL-Young E
Moderator
•
5421 Posts
•
37 Points
5362
0
Posted May 16th, 2021 19:00
Hi thanks for choosing Dell. Does the host name has an “_” or not? With and without, you could try test access to idrac FQDN. Wish you a good one!
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!franklinR530
3 Posts
5339
0
Posted May 17th, 2021 02:00
I can confirm this issue.
After updating to 2.80.80.80 access to the web ui via browser fails.
Max Mustermann
2 Posts
5292
0
Posted May 17th, 2021 03:00
I must also do an roll-back to get the iDrac working again.
/opt/dell/srvadmin/bin/idracadm7 -r -i rollback iDRAC.Embedded.1-1
DELL-Charles R
Moderator
•
4730 Posts
•
25476 Points
5231
0
Posted May 17th, 2021 10:00
Hello all,
Could you post an image of the error you get when FQDN is inaccessible please?
I'll have to escalate this up to the Systems Management Team.
DELL-Charles R
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Accept as Solution’. ‘Thumbs up’ the posts you like!
DELL-Shine K
6 Operator
•
3042 Posts
8259
1
Posted July 20th, 2021 02:00
@Philip-R , Are you using FQDN which is same as iDRAC DNS name and domain name configured on iDRAC.
This release have Host header security issue fix (Link) and launching iDRAC with hostname and FQDN will work by default if hostname/FQDN used is matching with DNS Name and Domain configured on iDRAC. If you are using a different name to launch iDRAC than one configured in iDRAC then you can add the hostname/FQDN used for launching as an exception by using below racadm command to make it work
To add hostname/FQDN as an exception
racadm set idrac.webserver.ManualDNSEntry test.domain.com
You can also disable host header check on iDRAC by running below command. This command will disable security fix of host header check (Link)
racadm set idrac.webserver.HostHeaderCheck Disabled