Some errors about realip HOT 3 CLOSED

Looks like your server is failing to connect to Google's servers so TCPShield can offset the time verification delay. I would suggest, for now, to go under your config and change timestamp-validation to system. However, I would look into other underlying causes to why you can't connect to the timestamp server. (Maybe firewalls, or request blocking by Google themselves)

from realip.

Looks like your server is failing to connect to Google's servers so TCPShield can offset the time verification delay. I would suggest, for now, to go under your config and change timestamp-validation to system. However, I would look into other underlying causes to why you can't connect to the timestamp server. (Maybe firewalls, or request blocking by Google themselves)

Thank you. Yes, my country can't connect to the Google server, because my country blocks all Google services. I will change the " timestamp-validation" to "system". It is recommended that you write this item into the plug-in configuration. It seems that the plug-in configuration on the official website config seems to be old.

from realip.

Looks like your server is failing to connect to Google's servers so TCPShield can offset the time verification delay. I would suggest, for now, to go under your config and change timestamp-validation to system. However, I would look into other underlying causes to why you can't connect to the timestamp server. (Maybe firewalls, or request blocking by Google themselves)

Thank you. Yes, my country can't connect to the Google server, because my country blocks all Google services. I will change the " timestamp-validation" to "system". It is recommended that you write this item into the plug-in configuration. It seems that the plug-in configuration on the official website config seems to be old.

I've edited the TCPShield documentation to include some information about timestamp validation.

from realip.