VMware Cloud Community
Heineken_
Contributor
Contributor

Error when connect whmcs with VIO

Hi, when I try to connect WHMCS witch  VIO, I got some error:

Compute No access to API Endpoint:http://xx.xx.xx.xx:8774/v2/8463fb2858654df79aa52****** with message: Connection Error:Connection timed out

Identity No access to API Endpoint:http://xx.xx.xx.xx:35357/v2.0 with message: Connection Error:Connection timed out

Image No access to API Endpoint:http://xx.xx.xx.xx:9292/v2 with message: Connection Error:Connection timed out

Network No access to API Endpoint:http://xx.xx.xx.xx:9696/v2.0 with message: Connection Error:Connection timed out

Volume No access to API Endpoint:http://xx.xx.xx.xx:8776/v2/8463fb2858654df79aa52****** with message: Connection Error:Connection timed out

Metering No access to API Endpoint:http://xx.xx.xx.xx:8776/v2/8463fb2858654df79aa52****** with message: Endpoints for this API interface are unavaiable

Please help me, thanks in advance!

Tags (2)
Reply
0 Kudos
3 Replies
Heineken_
Contributor
Contributor

This is my endpoint list

|            publicurl                        |            internalurl                |                adminurl                                                    |

+-----------------------------------------      +---------------------------------------+--------------------------------------------------------------------------------+

|        https://x.x.x.126:9696                   |        http://x.x.x.22:9696                   |        http://x.x.x.22:9696                    |

| https://x.x.x.126:8776/v1/%(tenant_id)s | http://x.x.x.22:8776/v1/%(tenant_id)s | http://x.x.x.22:8776/v1/%(tenant_id)s |

| https://x.x.x.126:8774/v2/%(tenant_id)s | http://x.x.x.22:8774/v2/%(tenant_id)s | http://x.x.x.22:8774/v2/%(tenant_id)s |

|      https://x.x.x.126:5000/v2.0              |      http://x.x.x.22:5000/v2.0              |      http://x.x.x.22:35357/v2.0             |

| https://x.x.x.126:8776/v2/%(tenant_id)s | http://x.x.x.22:8776/v2/%(tenant_id)s | http://x.x.x.22:8776/v2/%(tenant_id)s |

| https://x.x.x.126:8004/v1/%(tenant_id)s | http://x.x.x.22:8004/v1/%(tenant_id)s | http://x.x.x.22:8004/v1/%(tenant_id)s |

|        https://x.x.x.126:9292                   |        http://x.x.x.22:9292                    |        http://x.x.x.22:9292                    |

|        https://x.x.x.126:8000/v1               |        http://x.x.x.22:8000/v1               |        http://x.x.x.22:8000/v1               |

In WHMCS I can ping x.x.x.126 but can't ping x.x.x.22. But in my laptop I can ping both.

Please help! Thanks

Reply
0 Kudos
yjia
VMware Employee
VMware Employee

I'm not sure if I fully understand your question.

It seems like  you can ping your public VIP but you can't ping your internal VIP right?

Since the internal vip is only reachable on the management server which is as design.

Reply
0 Kudos
Heineken_
Contributor
Contributor

Thanks for your reply!

Can VMware Intergrated Openstack connect to WHMCS by "

WHMCS module for Openstack" ?

I use this module to connect VIO with WHMCS, but when connect it show that error.

When I connect to Public VIP, the system reply to internal VIP

Please help, thanks!!

Reply
0 Kudos