2.81.81.81 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
Hi! I just upgraded iDRAC on a (remote) T330. It was a big jump from 2.50.50.50 to 2.81.81.81 (a bit too big i guess hehe) Now i just see "400 Bad Request" when accessing the iDRAC web. I am guessing i can not fix this remotely.But can it be fixed by someone onsite? I dont have a Dell Tower here so cant experiment.Also that remote server only has iDRAC Express...
T330 iDRAC upgrade fail -> 400 Bad Request in web