Trouble logging in after installing self-manage using abctl on Linux

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

User is unable to login after installing self-manage using abctl on Linux. They are facing issues with the password generated by the ‘abctl local credentials’ command.


Question

Hi, i installed self manage using abctl on linux,
cant login using the password on this command

abctl local credentials

how to fix?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["self-manage", "abctl", "linux", "login", "password"]
2

few ideas
1)
you can try to uninstall
abctl local uninstall --persisted
and install again
abctl local install

  1. you can use overwrite password
    create secret.yaml
kind: Secret
metadata:
  name: airbyte-auth-secrets
type: Opaque
stringData:
  instance-admin-password: your-password```
then `abctl local install --secret secret.yaml`
wait for installation to finish and restart docker engine
3

hi guys, to me, I am using a hostname, and noticed that I can login while tunneling through localhost, but cannot if connecting using the hostname. I think some nginx defaults are a bit messy. Searching around, I think I see others facing similar problems.

Does it sound like your case, <@U07FRHURDA8>? Or you are running it in your local machine, connecting through localhost and still cannot login?

4

Hello <@U05JENRCF7C> will try this.

hey <@U03LNCXMQSY> i think same. cos base on the documentation using --host
when I use the custom host - after I put the initial info then I try to login using the email and the password i cant login. I think I will try the solution of above.

5

the above didn’t work to me, and frankly, I don’t see why it would. I think it has to do with nginx settings; a connection to api (for user auth) doesn’t go through if it tries to using your hostname, because either in the backend it still points to localhost, or because the requests, other than to localhost, get blocked

6

<@U03LNCXMQSY> really? Have you tried this https://docs.airbyte.com/deploying-airbyte/on-aws-ec2 the problem is its deprecated.

did you tried helm?

7

im still exploring this self-manage.

8

I have the same issue, stopping us from adopting airbyte.

9

I think I found something. It looks like security configuration in browsers.
I checked raw requests for localhost:8000 and airbyte.local:8000
When I compared requests I noticed that cookie with JWT and JWT_REFRESH_TOKEN wasn’t set for request to airbyte.local:8000
Cookie has attribute secure and I use http <http://airbyte.local:8000/>, and I can see information This attempt to set a cookie via a Set-Cookie was blocked because it had the "Secure" attribute but was not received over a secure connection.

Do you use http?

10

yes, http, obviously.

11

it is possible to turn off secure attribute on cookie
I found quite fresh change (2 weeks old)
https://github.com/airbytehq/airbyte-platform/blame/8a66a6a3568805e2af19bf1a126ff6f41cbf1d31/charts/airbyte-server/templates/deployment.yaml#L254

it worked on my machine with values.yaml like this

  auth:
    cookieSecureSetting: "false"```
12

That solved the long-lasting problem.

13

<@U05JENRCF7C> that is super helpful. Thanks!

14

Thank you <@U05JENRCF7C>, you are correct that secure cookies are the issue here. The documentation for Authentication has been updated with this information: https://docs.airbyte.com/deploying-airbyte/integrations/authentication#cookie-security-settings