[🐛 Bug]: API Tokenization refused on l-cidockerqa202.wpn.clarkinc.io and l-cidockerqa201.wpn.clarkinc.io

[tbuck-webstaurantstore]

Description

Credit Card Tokenization Calling API [POST]: https://tokenizer.dev.clarkinc.biz/v1/tokenize/creditcard is failing with "connection refused" for tests running on these servers:
l-cidockerqa202.wpn.clarkinc.io
l-cidockerqa201.wpn.clarkinc.io
https://qatools.dev.clarkinc.biz/Runs?id=3332042&filter=details

This same test ran successfully last night (7pm) on server:
l-cidockerqa106.wtn.clarkinc.io
https://qatools.dev.clarkinc.biz/Runs?id=3328535&filter=details

I suspect there is a firewall issue with servers 202, 201. Can you look at network/firewall configuration for 106 and set all other servers to match it?

Reproducible Code

// Tokenize credit cards
        creditCardList.each {
            tokenizedCreditCardDataMap.put(it, hpTokenizerHelper.tokenizeCreditCard(it))
            def lastEntry = tokenizedCreditCardDataMap.entrySet().last()
            log("Tokenized Credit Card Data: ${lastEntry.key} - ${lastEntry.value}", console_color_yellow)
        }

Debugging Logs

FAILED Verify: Tokenize Discover
IssueCategory: API_DATA
{
    "tokenizeDiscoverResponse": null
}
Called from: paymentprocessing.test.HpTokenizerHelper.tokenizeDiscover

These tests pass on other servers, but today (05/09/05) I seem to get only servers 201 & 202 every time I run my test suite: Payment Processing - EMD Test
https://qatools.dev.clarkinc.biz/ServerRunsSuite?id=973

---

ℹ️ Last known working version: 4.25.0 (revision 030fcf7918)

[selenium-ci]

@tbuck-webstaurantstore, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[github-actions]

⚠️ You reported using Selenium version 4.25.0 (revision 030fcf7918), but the latest release is 4.32.

Please verify that this issue still occurs with the latest version. If it no longer applies, you can close this issue or update your comment.

This issue will be marked "awaiting answer" and may be closed automatically if no response is received.

[selenium-ci]

💬 Please ask questions at:

• 📫 The Selenium user group
• 📮 StackOverflow
• 🗣 Our IRC/Slack/Matrix channels where the community can help you as well

[diemol]

Tagging it as a question because this does not seem related to Selenium at all.

[tbuck-webstaurantstore]

-- link removed for privacy --

This is probably an issue for SRE to fix. I opened the bug since I haven't gotten a response in the Teams chat listed above. Some selenium nodes do work:
l-cidockerqa205.wtn.clarkinc.io
l-cidockerqa206.wtn.clarkinc.io
l-cidockerqa103.wtn.clarkinc.io
l-cidockerqa102.wtn.clarkinc.io

Someone probably needs to check/coordinate with SRE to make sure there isn't a firewall issue with the nodes listed in my ticket?
l-cidockerqa202.wpn.clarkinc.io
l-cidockerqa201.wpn.clarkinc.io

[diemol]

The Selenium project is not responsible for that site.