Closed easoncxz closed 3 years ago
It seems very likely that I have somehow gotten my IP blocked by Google. From my server:
➜ ~ ping google.com
PING google.com (216.58.199.78) 56(84) bytes of data.
^C
--- google.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4086ms
➜ ~ curl -i https://www.google.com
^C
➜ ~ time curl -i https://www.google.com
^C
curl -i https://www.google.com 0.01s user 0.00s system 0% cpu 12.168 total
Resolution: it turns out that I have somehow manually listed an IP for google.com
in my /etc/hosts
, and the listed IP has become bad: that IP address does not seem to be Google's server's anymore.
dig
on my laptop results in good responses. This suggests that Google did not block my server's IP.After deleting the bad lines from my /etc/hosts
and flushing DNS cache (sudo systemd-resolve --flush-caches
, ReCaptcha is once again working on my server.
Clicking "Sign in with Twitter" leads to a long wait followed by an error response:
Reports of similar issues:
Official docs:
Server logs: (
journalctl -u twitanalysis
)Diagnosis
First guess is that it's something to do with IP addresses -- did Google just block my server's IP? Perhaps the extra
remoteip
param should be passed?