loft icon indicating copy to clipboard operation
loft copied to clipboard

Can't go past the "Complete your profile" page

Open rajish opened this issue 4 years ago • 3 comments

Submitting the form on the "Complete your profile" page spins the "Finish" button indefinitely. The loft pod logs say:

loft-6b647d94dc-ld6tl manager 2021-05-02 12:47:41.819818 I | http: TLS handshake error from 127.0.0.1:57608: remote error: tls: unknown certificate

I have TLS disabled in the values.yaml:

# TLS configuration with a custom cert and key
# Make sure the secret exists prior to deploying loft,
# otherwise the loft pod will not be able to start
tls:
  enabled: false
  secret: loft-tls
  crtKey: tls.crt
  keyKey: tls.key

...
ingress:
...
  tls:
    enabled: false
    secret: tls-loft
    clusterIssuer: lets-encrypt-http-issuer

rajish avatar May 02 '21 13:05 rajish

@rajish thanks for creating this issue! Are there any other logs? Are you running loft in a private cluster? The TLS handshare error is usually unrelated and occurs if you are using a self signed certificate that you have to accept in the browser first. However this shouldn't lead to a stuck "Finish" button. Does it work if you use Loft via the loft start portforwarding method?

FabianKramm avatar May 04 '21 10:05 FabianKramm

Yes, I'm trying to run loft on a private cluster. When I deleted it and installed it again the TLS messages stopped appearing, but the "spinning" problem persists.

I think it can have something to do with #112 as the cluster runs on AWS.

rajish avatar May 04 '21 13:05 rajish

@rajish thanks for the information! Usually the problem with private clusters is that you have to ensure that the following ports on the nodes are reachable because the kubernetes master needs to be able to communicate with the loft and kiosk pods directly (see our docs for more info):

  • 8888 (loft api service extension)
  • 8443 (kiosk api service extension)
  • 9443 (kiosk webhook & loft webhook)

In your case the problem is probably a hanging admission webhook as the Kubernetes master cannot reach the nodes subnet on one of the above mentioned ports. You can also take a look at our troubleshooting section that describes this problem as well.

FabianKramm avatar May 05 '21 09:05 FabianKramm

Going to close this out as its a bit old, but feel free to reopen if there are still issues here!

carlmontanari avatar Aug 19 '22 18:08 carlmontanari