1 Rookie
•
2 Posts
0
54
May 30th, 2025 22:13
After updating iDRAC access to iDRAC from Web UI fails with HostHeaderCheck enabled
Updated iDRAC on 10 R640 systems from 3.21.26.22 to 7.00.00.181.
iDRAC was updated successfully on all 10 systems.
3/10 systems ran across issue with accessing iDRAC with error.
All 10 systems have the same exact version of iDRAC and BIOS.
Error accessing iDRAC using IP from browser:
Bad Request
Your browser sent a request that this server could not understand.
Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.
Workaround:
We applied work around to disable HostHeaderCheck on the 3 systems, and that resolved the issue.
Our customer does not want this work around, because it's less secure.
I provided customer to execute “racadm set idrac.webserver.ManualDNSEntry 192.168.20.30 -> Replace the ip address with their iDRAC IP”
Followed by enabling HostHeaderCheck, but that did not resolve the issue.
Adding ManualDNSEntry did not resolve the issue with HostHeaderCheck enabled.
The only way we can access the iDRAC from Web UI is to disable HostHeaderCheck.
7/10 systems have no issue with HostHeaderCheck being enabled.
3/10 systems are at the same BIOS/iDRAC as the 7/10 systems that have no issue with HostHeaderCheck enabled.
Before the iDRAC update this issue did not exist on the 3 systems.
Need assistance to get the iDRAC Web access working with HostHeaderCheck set to enabled on the 3/10 systems.
Origin3k
4 Operator
•
2.2K Posts
0
June 6th, 2025 12:35
An today iDRAC can only be access trough its original IP, Name, Name+Domain. If you are coming from outside their Network and using a nat IP because you dont want to mess your own DNS you need to specify the IP/Names with the help of the idrac.webserver.ManualDNSEntry. I also have seen that incomplete config because Domain wasnt specified but Customer use a valid DNS Entry so the browser find the idrac... but idrac reponse with HTTP 400 BadRequest.
We have to service dozen of Hosts of our Customers with the help of a central OME Server or simple Browswer from inside our Network.
Origin3k
4 Operator
•
2.2K Posts
0
June 1st, 2025 10:57
You should specify multibple ManualDNSEntry settings like
DELL-Young E
Moderator
•
5.1K Posts
0
June 2nd, 2025 03:27
Hello, this may help.
PowerEdge: HTTP and HTTPS FQDN Connection Failures On iDRAC9 Firmware Version 5.10.00.00 | Dell US
Let us know if you have any further questions.
Respectfully,
pratik.sutaria
1 Rookie
•
2 Posts
0
June 3rd, 2025 19:53
@DELL-Young E @Origin3k ,
Thank you for the response.
I'm following the article.
racadm set idrac.webserver.ManualDNSEntry 192.168.20.30
192.168.20.30 is the IP address assigned to the iDRAC.
The work around should work as long as the iDRAC Web UI is accessing using the iDRAC IP of 192.168.20.30.
This is my understanding. Do I understand this correctly?
In this case, the iDRAC access using 192.168.20.30 is failing.
Respectfully,
DELL-Young E
Moderator
•
5.1K Posts
0
June 4th, 2025 02:05
Hello the article given is correct and you understand it correctly-need to have a manual DNS entry in iDRAC itself.
Respectfully,