Solved!
Go to SolutioniDRAC 9 version 6.10.00.00 400 Bad Request error
Hello,
We were asked by DELL supporter to update iDRAC again for a hardware support, from 6.02.00.00 to 6.10.00.00. After updating, the secure web access to iDRAC failed with error:
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.
After doing some tests, I have the following conclusions/workarounds:
1. the secure web access failed when using the FQDN of iDRAC interface
2. using the IP or short hostname works with the secure web access
3. setting iDRAC.WebServer.ManualDNSEntry to have the FQDN included won't solve the issue
4. disabling idrac.webserver.HostHeaderCheck aslo works, but could not open virtual console viewer
I tried to use racadm command 'sslresetcfg' to regenerate the certificate, but only short hostname used as Common Name (CN) and also only the short hostname listed in the DNS alternative name. By the way, we have DNS BMC/RAC Name and DNS Domain name correctly configured.
It looks like to me a new bug in version 6.10.00.00. Though there are not issues with the IP and short hostname access, it is still annoying since we have FQDN defined and linked everywhere.
Thanks,
Di
DELL-Young E
Moderator
•
5421 Posts
•
37 Points
2544
0
Posted February 1st, 2023 16:00
Hello this may help: https://dell.to/3jjZ1h0
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!Hello,
Unfortunately the knowledge base article https://www.dell.com/support/kbdoc/en-ca/000193619/http-https-fqdn-connection-failures-on-idrac9-firmware-version-5-10-00-00?dgc=SM&cid=376139&lid=spr8799951350&refid=sm_LITHIUM_spr8799951350&linkId=199564916 doesn't help. Before when we updated to 5.10.00.00, we met the same issue and this knowledge base article helped. However this time with 6.10.00.00, it seems different as I mentioned in my first post.
Di
Hello Charles,
Yes, I have reset the DRAC for many times in order to debug the issue and check the results of different configurations. The resets were done by racadm command line since we can still access with ssh.
The server mode is PowerEdge C6420, from download pages, the version 6.10.30.00 is still not available for me to download. When it is available, I definitely will try this version.
Thanks,
Di
DELL-Charles R
Moderator
•
4730 Posts
•
25476 Points
2492
0
Posted February 2nd, 2023 12:00
Hello Di Qing,
Have you reset the DRAC and check results?
How to Reset the Integrated Dell Remote Access Controller (iDRAC)
You may also try a flea power drain:
drain flea power (shut down, disconnect power cables and Network cables, hold in power button 20 seconds with cords removed). After flea power drain, system has to set for 3 minutes for DRAC to reset without any power plugged in, then plug in NIC and power but wait 2 minutes before power on to give DRAC time to initialize.
Would you let us know your server model? I see an iDRAC9 firmware 6.10.30.00 update but I don't know if it is for your model.
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
2485
0
Posted February 2nd, 2023 19:00
Can you share the FQDN used to access iDRAC and output of "racadm get idrac.webserver" command
The FQDN is "wns0054-drac.devices.t1", and the output of "racadm get idrac.webserver":
racadm>>get idrac.webserver
[Key=idrac.Embedded.1#WebServer.1]
BlockHTTPPort=Disabled
CustomCipherString=
Enable=Enabled
HostHeaderCheck=Enabled
Http2Enable=Disabled
HttpPort=80
HttpsPort=443
HttpsRedirection=Disabled
ManualDNSEntry=wns0054-drac,wns0054-drac.devices.t1
#MaxNumberOfSessions=8
SSLEncryptionBitLength=128-Bit or higher
Timeout=1800
TitleBarOption=Auto
TitleBarOptionCustom=
TLSProtocol=TLS 1.1 and HigherAs you can see, it's some internal domain name used here.
Thanks,
Di
I can confirm that we have the same issue as Di.
In the past, we have used the idrac.webserver.ManualDNSEntry workaround method described above (https://www.dell.com/support/kbdoc/en-ca/000193619/http-https-fqdn-connection-failures-on-idrac9-firmware-version-5-10-00-00?dgc=SM&cid=376139&lid=spr8799951350&refid=sm_LITHIUM_spr8799951350&linkId=199564916) for many of our Poweredge R640 and R650 servers running idrac firmware version 5.100 and above until 6.00.2.00, and it has always worked fine.
Now, after updating a new R650 server to idrac firmware 6.10.00, setting the ManualDNSEntry value does not work and returns the 400 Bad Request Error.
DELL-Young E
Moderator
•
5421 Posts
•
37 Points
2381
0
Posted February 7th, 2023 21:00
Hello, does this happen to a certain system only or to all?
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!
Di Qing
1 Rookie
•
13 Posts
4242
0
Posted May 23rd, 2023 09:00
Indeed, this seems fixed in later version. I just updated one of our nodes to version 6.10.80.00, the issue described in my first post has gone. When I was testing iDRAC version 6.10.30.00, the issue was sill there.