Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Remote SCP Displays Nothing #251

Open
Ktoks opened this issue Apr 25, 2024 · 3 comments
Open

[BUG] - Remote SCP Displays Nothing #251

Ktoks opened this issue Apr 25, 2024 · 3 comments
Assignees
Labels
backlog Implementation/fix not planned yet bug Something isn't working sorcery for those things which are kinda unexplainable

Comments

@Ktoks
Copy link

Ktoks commented Apr 25, 2024

Description

Upon connecting with SCP - the remote window is empty

Steps to reproduce

Select SCP - input server information, log into the server

Expected behaviour

Upon connecting with SCP - the remote window should show the contents of the default directory.

Environment

  • OS: Windows 10
  • Architecture: x86 Intel
  • Rust version: 1.77.2
  • termscp version: 0.13.0
  • Protocol used: SCP
  • Remote server version and name: Alma 8

Log

image

Additional information

None

@Ktoks Ktoks added the bug Something isn't working label Apr 25, 2024
@linconbb
Copy link

I've seen this error as well, while on my Ubuntu 22.04.
It's widely happened when communicating with old devices which only support SCP, such as Routers.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale issue closed due to inactivity label May 27, 2024
@veeso veeso added sorcery for those things which are kinda unexplainable backlog Implementation/fix not planned yet and removed stale issue closed due to inactivity labels May 27, 2024
@crazyrobo
Copy link

Also experiencing this issue. It's not showing SCP files on a Rocky 9 amd64 server, although it was before. Suddenly, just stopped working after disconnecting/reconnecting later. Nothing in logs, literally other than the connection message like @Ktoks. Attempted to clean and reinstall, nada. Not sure what's up, wondering if it's something like #246, although the default directory termscp connects to for this server does not have anything in it's permission strings other than "drwx".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Implementation/fix not planned yet bug Something isn't working sorcery for those things which are kinda unexplainable
Projects
None yet
Development

No branches or pull requests

4 participants