You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.
Hi there. I am having issues connected to my newly deployed Photon Platform. I am using the Windows CLI to connect to the load balancer, as indicated in the Quick Start Guide:
photon-windows-1.2-dd9d360.exe target login --username [email protected] --password 'xxxxx'
2017/08/27 19:36:46 Error: Get https://192.168.204.143:443/v1/system/auth: dial tcp 192.168.204.143:443: connectex: No connection could be made because the target machine actively refused it.
I saw another issue logged relating to iptables, but I have executed iptables.stop on all deployed VMs and still cannot connect. I can however ping all photon VMs from my workstation.
The text was updated successfully, but these errors were encountered:
@gregordavis I encounter this issue and I found the solution. You have to reboot the load balancer VM then the TCP port 443 and TCP port 4343 will enable. Also I use the Linux VM which deploy on ESXi hypervisor to login to photon-controller.
Hi there. I am having issues connected to my newly deployed Photon Platform. I am using the Windows CLI to connect to the load balancer, as indicated in the Quick Start Guide:
photon target set -c https://192.168.204.143:443
Response: API target set to 'https://192.168.204.143:443'
photon-windows-1.2-dd9d360.exe target login --username [email protected] --password 'xxxxx'
2017/08/27 19:36:46 Error: Get https://192.168.204.143:443/v1/system/auth: dial tcp 192.168.204.143:443: connectex: No connection could be made because the target machine actively refused it.
I saw another issue logged relating to iptables, but I have executed iptables.stop on all deployed VMs and still cannot connect. I can however ping all photon VMs from my workstation.
The text was updated successfully, but these errors were encountered: