Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

PCF Dev Login Failure #372

Open
gravidThoughts opened this issue May 6, 2019 · 6 comments
Open

PCF Dev Login Failure #372

gravidThoughts opened this issue May 6, 2019 · 6 comments
Assignees

Comments

@gravidThoughts
Copy link

gravidThoughts commented May 6, 2019

I am able to start the local pcfdev environment
cf dev start -f E:\pcfdev-v1.2.0-windows.tgz

Output

Creating the VM...
Starting VPNKit...
Starting the VM...
Waiting for the VM...
Deploying the BOSH Director...
Deploying PAS...
  Done (13m30s)
Deploying Apps-Manager...
  Done (1m14s)

         ██████╗  ██████╗███████╗██████╗ ███████╗██╗   ██╗
         ██╔══██╗██╔════╝██╔════╝██╔══██╗██╔════╝██║   ██║
         ██████╔╝██║     █████╗  ██║  ██║█████╗  ██║   ██║
         ██╔═══╝ ██║     ██╔══╝  ██║  ██║██╔══╝  ╚██╗ ██╔╝
         ██║     ╚██████╗██║     ██████╔╝███████╗ ╚████╔╝
         ╚═╝      ╚═════╝╚═╝     ╚═════╝ ╚══════╝  ╚═══╝
                     is now running!

        To begin using PCF Dev, please run:
            cf login -a https://api.dev.cfdev.sh --skip-ssl-validation

        Admin user => Email: admin / Password: admin
        Regular user => Email: user / Password: pass

        To access Apps Manager, navigate here: https://apps.dev.cfdev.sh

        To deploy a particular service, please run:
            cf dev deploy-service <service-name> [Available services: mysql,redis,rabbitmq,scs]

I noticed that the url in the above output does not match what you have in your getting started tutorial. I used what you have in the tutorial https://api.local.pcfdev.io. The following error occurs.

C:\WINDOWS\system32>cf login -a https://api.local.pcfdev.io --skip-ssl-validation
API endpoint: https://api.local.pcfdev.io
FAILED
Error performing request: Get https://api.local.pcfdev.io/v2/info: dial tcp 192.168.11.11:443: i/o timeout
TIP: If you are behind a firewall and require an HTTP proxy, verify the https_proxy environment variable is correctly set. Else, check your network connection.

As you can see, it appears to translates properly to 192.168.11.11:443. Interestingly, when I ping the url i get the following output.

Pinging api.local.pcfdev.io [192.168.11.11] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 24.249.237.25: Destination net unreachable.
Reply from 24.249.237.25: Destination net unreachable.

Networking is not my strong suit. Where is 24.249.237.25 coming from? Is this causing the issue with the login?

To be clear, I am not using a proxy.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@aemengo
Copy link
Contributor

aemengo commented May 6, 2019

Apologies but the tutorial that you are referencing is presenting the wrong url. The correct one to use is in fact the one that shows up on the splash message. Please do this instead:

cf login -a https://api.dev.cfdev.sh --skip-ssl-validation

@gravidThoughts
Copy link
Author

Thanks for the rapid reply.

e:\>cf login -a https://api.dev.cfdev.sh --skip-ssl-validation
API endpoint: https://api.dev.cfdev.sh
FAILED
Server error, status code: 404, error code: 0, message:

It looks like the DNS is properly set up.

e:\>ping api.dev.cfdev.sh

Pinging api.dev.cfdev.sh [10.144.0.34] with 32 bytes of data:
Reply from 10.144.0.34: bytes=32 time<1ms TTL=128
Reply from 10.144.0.34: bytes=32 time<1ms TTL=128
Reply from 10.144.0.34: bytes=32 time<1ms TTL=128
Reply from 10.144.0.34: bytes=32 time<1ms TTL=128

Are these 10.x addresses obtained using our internal DHCP server?

@aemengo aemengo self-assigned this May 10, 2019
@aemengo
Copy link
Contributor

aemengo commented May 10, 2019

It looks like something is listening on that IP (10.144.0.34) for you to get a 404 there. Do you think you're having an IP conflict with something else on your network? Either that or your instance of CF Dev has been compromised.

Are these 10.x addresses obtained using our internal DHCP server?

No, we have a route registered for that domain that resolves to that private IP.

@seymurfarziyev
Copy link

seymurfarziyev commented May 31, 2019

Similar issue happens on my Ubuntu v18.10 virtualbox machine:

osboxes@osboxes:~/workstation/pcf-dev-deploy$ sudo cf dev start -f pcfdev-v1.2.0-linux.tgz CF Dev is already running...

osboxes@osboxes:~/workstation/pcf-dev-deploy$ cf login -a https://api.dev.cfdev.sh --skip-ssl-validation API endpoint: https://api.dev.cfdev.sh FAILED Error performing request: Get https://api.dev.cfdev.sh/v2/info: dial tcp 10.144.0.34:443: i/o timeout TIP: If you are behind a firewall and require an HTTP proxy, verify the https_proxy environment variable is correctly set. Else, check your network connection.

I do not have any firewall or so blocking the mentioned IP.

@aemengo
Copy link
Contributor

aemengo commented May 31, 2019

@seymurfarziyev It looks like you had a failed startup, please try re-initializing with cf dev stop && cf dev start

Moreover, you shouldn't be using virtualbox. If not already, please consider the newest CF Dev offering that stands up a VM via native hypervisors.
https://github.com/cloudfoundry-incubator/cfdev

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants