CF_LOGIN_ISSUE

[Parthiban Annadurai]

Hi Devs,

            After a long struggle and because of all your kind and valuable help, am able to deploy CF successfully.. Now, am able to set the API EndPoint also but the problem is NOT ABLE TO LOGIN.. I dont know what to do for this issue..

FAYI,

CF: 202

Stemcell: ubuntu_trusty(2865)

IaaS: vSphere

Used MicroBOSH to deploy CF..

Could anyone please help on this issue??

Thanks in Well Advance..

[Johannes Hiemer]

Parthiban, please provide at least some basic debugging information like the results of 

CF_TRACE cf login

Or logs from your login instance.

The installation of CF is that complex, that reason for a non-working login is impossible to just "guess".

[Parthiban Annadurai]

@Johannes.. After my CF deployment, curl command shows the following,

curl api.192.168.33.54.xip.io/info

{"name":"vcap","build":"2222","support":"http://support.cloudfoundry.com","version":2,
"description":"Cloud Foundry sponsored by Pivotal",
"authorization_endpoint":"https://login.192.168.33.54.xip.io",
"token_endpoint":"https://uaa.192.168.33.54.xip.io","allow_debug":true}

and
using cf api https://login.192.168.33.54.xip.io i set the cf api.

Now, when am trying to login it shows as follows,

cf login

API endpoint: https://login.192.168.33.54.xip.io
FAILED
Error performing request: Get /login: unsupported protocol scheme ""


Not logged in. Use 'cf login' to log in.

Then, CF_TRACE=cf login command closes the terminal window itself unanimously..

Thanks in Well Advance..

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/fed9152d-e321-456d-9804-485f083e2d7a%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

[Parthiban Annadurai]

FAYI,

        My CF CLI version would be as follows,

cf -v
cf version 6.10.0-b78bf10-2015-02-11T22:26:40+00:00

Thanks..

[Parthiban Annadurai]

Hi All,

         Issue got solved by setting to the api api.192.168.33.54.xip.io

Thanks All..