{"id":726,"date":"2025-04-24T15:09:57","date_gmt":"2025-04-24T15:09:57","guid":{"rendered":"https:\/\/jadijkstra.nl\/?p=726"},"modified":"2025-04-24T15:10:02","modified_gmt":"2025-04-24T15:10:02","slug":"weird-issues-after-upgrading-omnissa-uag-to-2503","status":"publish","type":"post","link":"https:\/\/jadijkstra.nl\/index.php\/2025\/04\/24\/weird-issues-after-upgrading-omnissa-uag-to-2503\/","title":{"rendered":"Weird issues after upgrading Omnissa UAG to 2503"},"content":{"rendered":"\n<p>Recently I got a call from a customer who had issues with a new UAG deployment in a existing environment.<\/p>\n\n\n\n<p>The problem they faced was: HTTP 400 Error<\/p>\n\n\n\n<p>According to the Omnissa Documentation, the Changes in Host Header Validation could be a valid point to start.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" loading=\"lazy\" width=\"1024\" height=\"275\" src=\"https:\/\/jadijkstra.nl\/wp-content\/uploads\/2025\/04\/image-1024x275.png\" alt=\"\" class=\"wp-image-727\" srcset=\"https:\/\/jadijkstra.nl\/wp-content\/uploads\/2025\/04\/image-1024x275.png 1024w, https:\/\/jadijkstra.nl\/wp-content\/uploads\/2025\/04\/image-300x81.png 300w, https:\/\/jadijkstra.nl\/wp-content\/uploads\/2025\/04\/image-768x206.png 768w, https:\/\/jadijkstra.nl\/wp-content\/uploads\/2025\/04\/image.png 1080w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>But&#8230;<\/p>\n\n\n\n<p>The host Header Validation looks good&#8230; domain name filled in, ip-address filled in&#8230; no issue here (but?)<\/p>\n\n\n\n<p>When we go to the command line interface, we do a : adminreset &#8211;allowedHostHeader uag1.example.com,uag-lb.example.com<\/p>\n\n\n\n<p>And what happens next, the interface says : updated [NULL}, to uag1.example.com,uag-lb.example.com<\/p>\n\n\n\n<p>So for some reason, the information in the backend of the UAG is corrupted or something, representing the data in de UAG but not working resulting in a HTTP 400 error.<\/p>\n\n\n\n<p>I think this has to do in my situation the host was not in FQDN!<br>So whenever this issue occurs, please try to update the allowd hosts headers through the commandline to verify if the information is correct!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Recently I got a call from a customer who had issues with a new UAG deployment in a existing environment. The problem they faced was: HTTP 400 Error According to the Omnissa Documentation, the Changes in Host Header Validation could be a valid point to start. But&#8230; The host Header Validation looks good&#8230; domain name [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/posts\/726"}],"collection":[{"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/comments?post=726"}],"version-history":[{"count":1,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/posts\/726\/revisions"}],"predecessor-version":[{"id":728,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/posts\/726\/revisions\/728"}],"wp:attachment":[{"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/media?parent=726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/categories?post=726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jadijkstra.nl\/index.php\/wp-json\/wp\/v2\/tags?post=726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}