 Kor
WPML Supporter since 08/2022
Languages:
English (English )
Timezone:
Asia/Singapore (GMT+08:00)
|
Thanks for your reply. You can refer to the list of domains here https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/ . Usually, whitelisting the domains should be enough.
|
 hadiE-2
|
Hi Team,
The hosting provider team got back to me with the following:
The CloudLinux team and the software engineer assigned to the case have allowed all IPs under Immunify360, and they even went as far as to completely disable and shut down Immunify360 temporarily, but the api.toolset.com remains inaccessible.
Would it be possible for you to contact WPML and ask them to check if the server IP 192.169.172.41 is by any chance blocked by the api.toolset.com service?
Appreciate if you can test the IP above is blocked by api.toolset.com?
Appreciate your kind support.
Kind Regards,
Hadi
|
 Kor
WPML Supporter since 08/2022
Languages:
English (English )
Timezone:
Asia/Singapore (GMT+08:00)
|
Thanks for your reply. I've forwarded this to our 2nd Tier Support and they will check and revert back to us as quickly as possible.
|
 hadiE-2
|
Hello Team,
Any update on my inquiry above?
Appreciate your soonest response.
Kind Regards,
Hadi
|
 Kor
WPML Supporter since 08/2022
Languages:
English (English )
Timezone:
Asia/Singapore (GMT+08:00)
|
Thanks for your reply. I have some feedback from our 2nd Tier Support. This is what they mentioned.
I checked our API logs for Toolset for the past two weeks and found no activity from the IP address 192.169.172.41 provided by the client, nor from the domain hidden link. This means our system has not received any requests from this website or IP.
Could you confirm why the client is trying to access the Toolset API? Has the client registered any Toolset plugins other than Types? Do they have a Toolset account?
I also checked our WAF and API activity for WPML for the past week and found no activity from either the IP or the domain.
|