Multicast address (224.0.0.1) cannot be tested via this interface! at /usr/local/cpanel/Cpanel/IP/Bound.pm line 54.
Multicast address (224.0.0.1) cannot be tested via this interface! at /usr/local/cpanel/Cpanel/IP/Bound.pm line 54.
How to fix this issue
-
Hey hey! Can you get me more details on where this error was and what work you are trying to perform? 0 -
Hey hey! Can you get me more details on where this error was and what work you are trying to perform?
While doing cpkeyclt I'm getting this error0 -
Thanks for the additional details. It seems like there is an issue with the networking configuration on the machine as outbound requests from your system should always be made over a public IP address. You can run the following command to see what IP address is making the outbound connection to the cPanel license network: curl -w '\n' -s http://myip.cpanel.net:2089/v1.0/
If that shows an IP address that you aren't expecting, you may need to adjust the routing on the server to change that. To see the current routing tables you can run the "route -n" command.0 -
Thanks for the additional details. It seems like there is an issue with the networking configuration on the machine as outbound requests from your system should always be made over a public IP address. You can run the following command to see what IP address is making the outbound connection to the cPanel license network:
curl -w '\n' -s http://myip.cpanel.net:2089/v1.0/
If that shows an IP address that you aren't expecting, you may need to adjust the routing on the server to change that. To see the current routing tables you can run the "route -n" command.
I could see the server IP while running the command route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 91.134.24.254 0.0.0.0 UG 0 0 0 eth0 91.134.24.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth00 -
I'm not finding much for that "multicast" error you mentioned. If that is the only output from the cpkeyclt command it might be best to open a ticket with our team to get this checked out. If you do that, let us know the ticket number here so we can post the fix once the issue is resolved. 0
Please sign in to leave a comment.
Comments
5 comments