appleboy / appleboy/scp-action
[BUG] recent versions establish too many connections and cause timeouts (when UFW is used)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.6k
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
When UFW is used as firewall timeouts occur ( #106 #69 #77 #29 #17 ...) since the firewall's rate limiting kicks in if more than 6 connections within 30 seconds are established:
ufw supports connection rate limiting, which is useful for protecting against brute-force login attacks. When a limit rule is used, ufw will normally allow the connection but will deny connections if an IP address attempts to initiate 6 or more connections within 30 seconds.
Typical usage is: ufw limit ssh/tcp
-- https://manpages.ubuntu.com/manpages/noble/en/man8/ufw.8.html
There are several work-arounds:
- downgrading to an older version such as
appleboy/scp-action@v0.1.3 - inceasing the
timeout to 90 secondsor more - disabling the brute-force protection in the firewall via
ufw ALLOW ssh/tcp- don't do this.
These workarounds address the timeout symptoms but fail to resolve the underlying issue. The core problem lies in the establishment of a new connection for every request. Instead, the initial SSH connection should be reused.
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name files, tests, or an entry point. Trace where the action establishes SSH connections and inspect how requests are handled; done means the initial SSH connection is reused so repeated requests no longer trigger UFW rate-limit timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100