-
Notifications
You must be signed in to change notification settings - Fork 426
Open
Description
Bug Description
Connection fails when the FTP username is in the form user@subdomain.domain.tld , but the same deploy works when using user@domain.tld. Server and password are unchanged; only the username format differs. So the action appears to mishandle or reject usernames that include a subdomain before the @.
My Action Config
on: push
name: Publish Website
jobs:
web-deploy:
name: Deploy website every commit
runs-on: ubuntu-latest
environment: prod
steps:
- uses: actions/checkout@v4
- name: Deploy via FTP
uses: SamKirkland/FTP-Deploy-Action@v4.3.5
with:
server: server111.shared.spaceship.host
username: user@subdomain.domain.tld
password: ${{ secrets.FTP_PASSWORD }}
server-dir: ${{ secrets.FTP_REMOTE_PATH }}
exclude: |
**/.git*
**/.git*/**
**/node_modules/**
log-level: verboseMy Action Log
----------------------------------------------------------------
π Thanks for using ftp-deploy. Let's deploy some stuff!
----------------------------------------------------------------
If you found this project helpful, please support it
by giving it a β on Github --> https:***github.com***SamKirkland***FTP-Deploy-Action
or add a badge π·οΈ to your projects readme --> https:***github.com***SamKirkland***FTP-Deploy-Action#badge
Failed to connect, are you sure your server works via FTP or FTPS? Users sometimes get this error when the server only supports SFTP.
----------------------------------------------------------------
-------------- π₯π₯π₯ an error occurred π₯π₯π₯ --------------
----------------------------------------------------------------
----------------------------------------------------------------
---------------------- full error below ----------------------
----------------------------------------------------------------
Error: Timeout (control socket)
at Socket.<anonymous> (***home***runner***work***_actions***SamKirkland***FTP-Deploy-Action***v4.3.5***dist***index.js:5299:33)
at Object.onceWrapper (node:events:638:28)
at Socket.emit (node:events:524:28)
at Socket._onTimeout (node:net:595:8)
at listOnTimeout (node:internal***timers:581:17)
at process.processTimers (node:internal***timers:519:7)
Error: Error: Timeout (control socket)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels