Unable to connect to remote server for previously connected servers
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 245
- Forks
- 41
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
Forge CLI Version
1.8.0, 1.8.3
PHP Version
8.4.5
Description
I have 9 servers in forge and face some weird behavior with forge CLI tool - I just can not connect to some servers.
It only connects once I delete SSH key from server and do ssh:configure. I can then connect once, but once i disconnect and try to connect back i can again see this error:
Unable to connect to remote server. Maybe run [ssh:configure] to configure an SSH Key?
Sometimes it works consistently though, but then I can not connect to the previously connected servers.
Overall it just feels like there some some or limit for connected servers and once you add more one of the previous ones is getting removed!
Pls let me know what other details I can provide in order to find the root of the issue.
Steps To Reproduce
- Configure ssh for multiple servers (it feels like i started experiencing this once i've got more than 5 servers)
- Try to connect to all of them one by one
- At some point you should get following error: Unable to connect to remote server. Maybe run [ssh:configure] to configure an SSH Key?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the forge CLI SSH connection flow and the ssh:configure entry point. Reproduce the problem by configuring more than five servers and connecting to them one by one, then inspect how previously connected servers are retained. Done means repeatedly connecting to all configured servers without losing access or showing the SSH configuration error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100