Plugin Author
edo888
(@edo888)
Hi,
You will need to make sure that you do not block our proxy IP addresses, otherwise we will not be able to access your website and translate it. Please contact our live chat for the full list: https://gtranslate.io/#contact
Please consult your firewall/hosting support about it. You will need to add our IP addresses into a trusted proxy list and use the X-Real-IP or X-GT-ClientIP header, which has the real visitor IP address and do the decisions based on that instead.
If your hosting provider or firewall support are not able to help you, consider using Cloudflare for your website, which usually solves this kind of issues.
Thanks! 🙂
Hi there, thanks for the prompt reply.
Will contact your live chat for the full list: https://gtranslate.io/#contact
Kind regards,
got it https://gtranslate.io/?xyz=998#
(does not work in all browsers)
-
This reply was modified 4 years, 7 months ago by
mbzo2006.
Plugin Author
edo888
(@edo888)
Not sure what doesn’t work for you.
You can also contact us through your GTranslate dashboard: https://my.gtranslate.io
Thanks! 🙂
Got it, thanks! (Intercom chat popup was blocked by Ghostery)
Ok, so via the Live Chat we managed to get a full list of IPs that apparently need to be whitelisted in order that Gtranslate can function properly.
However, the hosting provider and Digital Ocean are unaware of any specific IP blocking issues. According to the hosting provider there are no such blocks and they question the need for whitelisting IPs.
According to Gtranslate plugin uses standard ports to establish server communication.
Gtranslate also suggest using Cloudflare to serve as a proxy, so the hosting servers see Cloudflare IPs instead of Gtranslate, and they’re able to get the content of the website.
The issue is not resolved.
-
This reply was modified 4 years, 7 months ago by
mbzo2006.
-
This reply was modified 4 years, 7 months ago by
mbzo2006.
-
This reply was modified 4 years, 7 months ago by
mbzo2006.
Thanks to Gtranslate support team for resolving this issue. Solution was to use Sub-domain URL structure: http://es.example.com/ instead of sub-directory, adding indivdual CNAME records to domain registrar for each language needed.
The hosting company was not able to explain why the Gtranslate IPs were identified as “malicious”.
-
This reply was modified 4 years, 7 months ago by
mbzo2006.
-
This reply was modified 4 years, 7 months ago by
mbzo2006.