Google Website Translator - 502 Bad Gateway - google-translate

I've got the Google Website translator widget on my site (www.ancient.eu.com). It used to work perfectly, but now I am not getting any translations. When I check the Chrome Console I see the following errors:
POST http://translate.googleapis.com/translate_a/t?anno=3&client=te&format=html&v=1.0&scid=e669185dd7423a09-043358cb90b67c5d-g813cc84edafdd3ce-12&logld=v10 502 (Bad Gateway 51001) element_main.js:248
XMLHttpRequest cannot load http://translate.googleapis.com/translate_a/t?anno=3&client=te&format=html&v=1.0&scid=e669185dd7423a09-043358cb90b67c5d-g813cc84edafdd3ce-12&logld=v10. Origin http://www.ancient.eu.com is not allowed by Access-Control-Allow-Origin.
Does anyone know what went wrong here?
Thanks for your help.
Jan

Related

Getting Status 504 using Rest Routing API

Since today other people and me are getting 504 Response / Timeout while using the Rest Routing API.
Yesterday everything worked fine. When I try to call the API via Browser I also get 504 Gateway Timeout.
Other APIs are working as expected. It's only the Routing API which fails with 504.
Requests are sent from Germany.
The status page shows that everything is up and running, but the Routing API is unreachable.
It started to work again as it should 3 minutes ago..
So I think the problem was solved by here.com ..

Need some solution for resolving a 404 error of WordPress AMP

I'm a beginner of AMP from Japan.
Now I'm in trouble dealing with a error that is output when I introduce AMP into my WordPress webpage.
I cloud activate the AMP plugin and display an AMP of the post page without problem.
But the following error was output on my browser console when I added #development=1 to the end of URL of the post AMP to confirm whether the post AMP was configured as a valid AMP on Google.
Failed to load resource: the server responded with a status of 404 ()
https://cdn.ampproject.org/v0/validator_minified.js.sourcemap
Then I accessed to the above URL described in the error message, the following error page was displayed.
Google
404. That’s an error.
The requested URL /v0/validator_minified.js.sourcemap was not found on this server. That’s all we know.
I guess the output post AMP may not be recognized by Google as a structure of AMP if this error page was displayed.
But I have no idea to resolve the 404 error and can't progress any more.
In other words, I'd like to know some solution and hints to resolve the 404 error in order that Google recognizes my post AMP.
If you have some solution or hints, I'd be very helpful if you provide them for me.
Thanks in advance.
clear your cache in the server and delete your log. Blocking an malicious IP trafics and your see the IP in 30 per connection then you want blocked the IP.
Using proxy or like mitigation

Wordpress Ninja Forms, Access-Control-Allow-Origin and admin-ajax.php

So, I have this WP installed on Heroku and I've installed Ninja forms to it. Despite everything working OK locally, when I push it to Heroku, the form is not submited and I receive this error through the Chrome's Console:
Failed to load https://ratts.com.br/wp-admin/admin-ajax.php: No
'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'http://ratts.com.br' is therefore not allowed
access. The response had HTTP status code 503.
It's worthy to mention that this error is only delivered when I access the page via http, but when I access the page trough https the form works just fine, due to what I think to be a CORS problem. Anyone has any idea about how can I solve this issue? It have been three days of unsuccessful research already... rsrs
I believe that http to https for the same domain is still considered CORS. You need to make sure all traffic is redirected from http to https. Take a look at this thread.

Wordpress site returns status 500 but still works

http://ststephens.edu/
This site returns status code 500 (Internal Server Error) when I do
wget http://ststephens.edu/ but works fine on my browser. Also as seen in this screenshot, clearly the homepage is a 500 status but the site seems functional.
What could make this happen?
Web browsers are more flexible then wget. Even if it receives an error code, it will still display the page content returned along with the error code response. Web servers only fall back on their default error view if no content is provided.
Wget and search engine crawlers are more strict. They will bail out as soon as they see the error code response.
I think there is a problem with your server configuration. Check your web server log file. It may tell you why the server gave this error.

Fiddler: Error 502 Proxy Error

I am using Fiddler to debug all HTTP request of my ASP.NET application.
For a while (about 6 months) I had no problem. All HTTP requests appeared on Fiddler and so on.
The last two days Fiddler stoped working :/ Always returns the same error: "The request failed with HTTP status 502: Proxy Error ( The ISA Server denied the specified Uniform Resource Locator (URL). )."
The strange thing is that only happens to my application, i. e. all HTTP requests from youtube, email, etc, appear on Fiddler.
What is the problem here?
From my case adding this line on OnBeforeRequest function in Fiddler Script fixed it for me,
oSession["x-OverrideSslProtocols"] = " ssl3;tls1.0;tls1.1;tls1.2";
I had the same issue with Fiddler - my HTTPS site worked fine in IE, however got 502 error in Chrome. After analyzing the issue, I found that has manual proxy enabled in Fiddler (not recommended):
Tools -> Fiddler Options -> Gateaway
it was the root cause of this strange behavior. Switching to "System Proxy" made this working for both IE and Chrome.
I had a scenario where production url was https and test was http.
When wrongly calling test with https in fiddler then I got 502 and ended here on stack overflow.
I will just leave this here in case anyone else does the same mistake.
I solved my problem =)
I seems that something changed at my company network. So I changed the file CustomRules.js from Fiddler and added some lines at OnBeforeRequest.
Now, everything works just fine
Best regards.

Resources