Good day.
Please check if ]https://flashphoner.com is available from the server on which update command failed.
Usually, update works as follows:
1. Check if site is available
2. Download latest version number
3. Compare latest version number with current one
4. Proceed to download update if version numbers are different.
So, the most possibel reason is site availability.
The site/domain is available and current version is 5.2.616. However, the update function still doesn't work:
[root@vmXXXXXX ~]# ping flashphoner.com
PING flashphoner.com (188.166.201.77) 56(84) bytes of data.
64 bytes from 188.166.201.77 (188.166.201.77): icmp_seq=1 ttl=58 time=4.76 ms
64 bytes from 188.166.201.77 (188.166.201.77): icmp_seq=2 ttl=58 time=4.33 ms
64 bytes from 188.166.201.77 (188.166.201.77): icmp_seq=3 ttl=58 time=4.31 ms
^C
--- flashphoner.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 4.315/4.471/4.767/0.222 ms
[root@vmXXXXXX ~]# sudo service webcallserver update
>>> You have latest version: 5.2.615-b4908763858a329d6ea6967be32593fa4dc14bce
Outbound traffic is not limited on this machine, so any outbound traffic is not rejected by the firewall.
On the AWS machine, the update works as expected:
[ec2-user@ip-XXX-XX-XX-XX ~]$ ping flashphoner.com
PING flashphoner.com (188.166.201.77) 56(84) bytes of data.
64 bytes from 188.166.201.77: icmp_seq=1 ttl=43 time=8.71 ms
64 bytes from 188.166.201.77: icmp_seq=2 ttl=43 time=8.37 ms
64 bytes from 188.166.201.77: icmp_seq=3 ttl=43 time=8.20 ms
^C
--- flashphoner.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 8.203/8.431/8.715/0.212 ms
[ec2-user@ip-XXX-XX-XX-XX ~]$ sudo service webcallserver update
>>> New version available: 5.2.616
>>> Your version: 5.2.610
>>> You have to stop FlashphonerWebCallServer before update.
>>> Stop now [yes/no] ?
----------------
/edit:
As you can see, the machine where the update function doesn't work, states the version as:
5.2.16-hashversion
whereas on the AWS EC2 instance the version number is normal, without hash.
After updating the AWS EC2:
[ec2-user@ip-XXX-XX-XX-XX ~]$ sudo service webcallserver update
>>> You have latest version: 5.2.616
No hash. I don't know if this difference is significant.
