ledokku: Can't leave ssh connection page

Bug report

Describe the bug

Just finished the setup using the bootstrap and everything worked fine, however, the ssh connection page never leaves and I did already registered the ssh-key provided in that same page.

Screenshot 2021-02-25 at 13 46 34

I have this two ssh key added:

SHA256:... NAME="admin1" ...
SHA256:... NAME="ledokku" ...

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (11 by maintainers)

Most upvoted comments

2021-03-06T00:13:53.015163881Z app[web.1]: yarn run v1.22.5
2021-03-06T00:13:53.056599420Z app[web.1]: $ yarn prisma:migrate && node build/index.js
2021-03-06T00:13:53.241683999Z app[web.1]: $ prisma migrate up --experimental
2021-03-06T00:13:53.735597864Z app[web.1]: 
2021-03-06T00:13:54.260994957Z app[web.1]: Prisma schema loaded from prisma/schema.prisma
2021-03-06T00:13:54.408645297Z app[web.1]: šŸ‹ļøā€  migrate up
2021-03-06T00:13:54.408664401Z app[web.1]: 
2021-03-06T00:13:54.409014804Z app[web.1]: All migrations are already applied
2021-03-06T00:13:55.305978659Z app[web.1]: šŸš€ Server ready at http://localhost:4000/graphql
2021-03-06T00:13:55.306112384Z app[web.1]: šŸš€ Subscriptions ready at ws://localhost:4000/graphql
2021-03-06T00:14:26.903904034Z app[web.1]: 2021-03-06T00:14:26.903Z queries:setup Error: connect EADDRNOTAVAIL [MY IPV6 ADDRESS] - Local (:::0)
2021-03-06T00:14:26.903930897Z app[web.1]:     at internalConnect (net.js:923:16)
2021-03-06T00:14:26.903936539Z app[web.1]:     at defaultTriggerAsyncIdScope (internal/async_hooks.js:364:12)
2021-03-06T00:14:26.903940692Z app[web.1]:     at net.js:1011:9
2021-03-06T00:14:26.903944177Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:79:11)

Iā€™m having the same issue too but I believe that it may be because of the ipv6 address that it defaults to.

Edit: The fix is to add the actual hostname/ip: dokku config:set ledokku DOKKU_SSH_HOST=<your hostname/ip>

@Akirtovskis Yeah perhaps regenerating the ssh would work, I might try.

@pradel That would be amazing and would possibly avoid creating issues on Github that are probably not issues, like mine šŸ˜