The update package does not work.
Csf-u command to get the following answer:
Oops: Unable to download: Can not connect to http://wxwxw.configserver.coxm:80 (timeout)
Ping the site works correctly
The X between letters were placed to prevent the post appears to contain links
root @ server1 [~] # csf-u
Oops: Unable to download: Can not connect to http://wxwxw.configserver.coxm:80 (timeout)
root @ server1 [~] # ping-c5 http://wxwxw.configserver.coxm
Configserver.coxm PING (85.13.195.235) 56 (84) bytes of data.
64 bytes from server.configserver.nxet (85.13.195.235): icmp_seq = 1 ttl = 56 time = 4.95 ms
64 bytes from server.configserver.nxet (85.13.195.235): icmp_seq = 2 ttl = 56 time = 4.70 ms
64 bytes from server.configserver.nxet (85.13.195.235): icmp_seq = 3 ttl = 56 time = 4.84 ms
64 bytes from server.configserver.nxet (85.13.195.235): icmp_seq = 4 ttl = 56 time = 4.82 ms
64 bytes from server.configserver.nxet (85.13.195.235): icmp_seq = 5 ttl = 56 time = 4.86 ms
--- Ping statistics --- configserver.coxm
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min / avg / max / mdev = 4.708/4.837/4.950/0.099 ms
csf -u fail
Re: csf -u fail
Same happening to me too, this seems to be a common occurrence.
Re: csf -u fail
me too.. occurred to me that since CSF is a firewall, despite me not having blocked their ip address ... could it possibly be blocked?
Indeed it is, but how?
Also explains why I have not received any activation emails from this support forum.
This is distinctly a "gotcha" for new users (meaning me).
Turns out configserver com's ip address is inside a CIDR range that I have marked as Russian, and blocked.
So I have let the Russians rush in for now.
and put configserver com's ip address in csf.ignore, which presumably should mean it never gets blocked again, even if it is, it won't be.
How did I get caught out like this I wondered? While I had entered the ip address given to me by tptb it turns out it is not the same ip address as configserver com. On reflection this is no surprise, but did not occur to me at the material time (i.e. when entering ip addresses to be trusted (ignored).
ant.
Indeed it is, but how?
Also explains why I have not received any activation emails from this support forum.
This is distinctly a "gotcha" for new users (meaning me).
Turns out configserver com's ip address is inside a CIDR range that I have marked as Russian, and blocked.
So I have let the Russians rush in for now.
and put configserver com's ip address in csf.ignore, which presumably should mean it never gets blocked again, even if it is, it won't be.
How did I get caught out like this I wondered? While I had entered the ip address given to me by tptb it turns out it is not the same ip address as configserver com. On reflection this is no surprise, but did not occur to me at the material time (i.e. when entering ip addresses to be trusted (ignored).
ant.