Hello,
We need to secure the connection between TestOps and GitLab, but first we need to whitelist https://testops.katalon.io/ in our system.
Could you please provide a range of IP addresses ?
regards
Hi @kmutar,
Thank you for sharing this. You can check the following link:
Please let me know if this helps.
To be noticed that, the documentation page at:
may be misleading.
At the time of writting, i get this:
$ ping testops.katalon.io
PING testops.katalon.io (52.1.165.1) 56(84) bytes of data.
^C
--- testops.katalon.io ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1051ms
$ ping testops.katalon.io
PING testops.katalon.io (34.197.125.64) 56(84) bytes of data.
^C
--- testops.katalon.io ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1033ms
$ ping testops.katalon.io
PING testops.katalon.io (52.1.165.1) 56(84) bytes of data.
^C
--- testops.katalon.io ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2086ms
$ ping testops.katalon.io
PING testops.katalon.io (34.197.125.64) 56(84) bytes of data.
^C
--- testops.katalon.io ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1013ms
Ignore the ping response, note that the IP’s are rotating.
From what I know, those are Elastic IP’s assigned by AWS, looks familiar to me.
Even if today you may get a list of apparently ‘stable’ 3 of them, this can change in the future.
As proved, they don’t match any longer with the ones documented in the mentioned link.
Therefore, your discussion with the IT team is a bit more challanging, you have to whitelist by domain as documented.
Have fun!
Thanks !
I can see there is a long debate.
Just to bring more materials to our problem we are facing, our GitLab repository is not accessible publicly. As you see in the screenshot, TestOps is unable to connect to our gitlab.****.com repo :
Whitelisting by domain is not really a solution, are you able to provide fixed IPs ?
we can take a look also at the DNS server discovered:
$ dig testops.katalon.io
; <<>> DiG 9.18.12 <<>> testops.katalon.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29710
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;testops.katalon.io. IN A
;; ANSWER SECTION:
testops.katalon.io. 60 IN A 52.1.165.1
testops.katalon.io. 60 IN A 34.197.125.64
;; Query time: 37 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Tue Mar 14 16:08:53 EET 2023
;; MSG SIZE rcvd: 79
Interresting, not one but two A records are used, which is against recomended practice by AWS.
With elastic IP’s CNAME’s should be used instead
Good luck with this, I already demo’ed why :))))
I am confused by your discussion.
Which direction of IP connection initiation are you talking about?
Let me set the point of view. Let’s assume we are the GitLab server of @kmutar.
@bionel seems to be talking about the outgoing IP connection from the GitLab server to TestOps.
@kmutar seems to be talking about the incoming IP connectio from the TestOps to the GitLab server.
We should clearly seperate these 2 directions, we should not mix them.
The following Katalon’s documetations are also confusing. I can not see which direction of IP connetion these documents are talking about.
Are these documents correct?
Have you seen the following? :
I have and we still have the same debug error log
you are the confused one.
katalon is using elasting ip’s with A records.
read about this.
it was supposed you are an AWS expert since you love it apparently
I hope the Katalon’s official documentations to describe everything clearly enough and resolve all of my confusions.
I only hope that I am wrong regarding Elastic IP’s, anyway, I will throw this here.
For reliable 24/7 services, usage of global static IP is a better approach: