- CheckMates
- :
- Products
- :
- Developers
- :
- API / CLI Discussion
- :
- Set UserCheck URL via API fails DNS check
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Set UserCheck URL via API fails DNS check
When running:
set-simple-gateway usercheck-portal-settings.portal-web-settings.main-url "https://hostname.tld/UserCheck"
the command fails with generic_error and "DNS failed to resolve the hostname: hostname.tld."
I've checked with tcpdump and the SmartCenter is resolving this name correctly.
Setting the Main URL field via SmartConsole succeeds.
Setting other hostnames, like www.cnn.com, work.
I use hostname.tld on multiple gateways, as all of them are contained behind the same load balancer in Azure.
api.elg and cpm.elg confirm the issue is related to gateway_legacy.portals_manager.PortalRequestsValidationHelper.
Anyone seen something similar?
The goal is to set a name and certificate for UserCheck in Azure Scale Set gateways.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I opened a case for it and got the information that a Hotfix is available on request and that the fix will be integrated in a future Jumbo (PRHF-28814, PMTR-91949).
kr, Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Omer_Kleinstern what say you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you run the command on your SMS or on another machine? If the former, please take this with TAC. If the latter, you may need to set up the name on the client as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This script is to be run as part of CME, so it is only run on the SMS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Understood, please take this with TAC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you been able to find a solution for this? I've got the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
No, I gave up on this.
Can confirm the issue still persists on R81.20 in my lab.
Best regards,
Harald
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I opened a case for it and got the information that a Hotfix is available on request and that the fix will be integrated in a future Jumbo (PRHF-28814, PMTR-91949).
kr, Bernhard
