The least intensive way is to login directly with the root. Preferably using a public key authentication.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- stady234
When using SFTP – I can connect, navigate, and use the PuTTY shell (automatic open). I have been able to "sudo" in the PuTTY shell and after re-entering the password, complete any command needed.
However when trying to edit file contents or add new files (anywhere) I constantly get "permission denied: Error code 3". I have tried multiple ways to get authenticated, but my knowledge is limited.
Under the SFTP section: if I change the "server" dropdown to anything but default I get
I am trying to find the LEAST intensive solution to allow full access under the newer rasbian version, like I had before stretch... I don't particularly care what WAY/protocol I need to use, so long as it provides the functionality.
However when trying to edit file contents or add new files (anywhere) I constantly get "permission denied: Error code 3". I have tried multiple ways to get authenticated, but my knowledge is limited.
Under the SFTP section: if I change the "server" dropdown to anything but default I get
Cannot initialize SFTP protocol. Is the host running an SFTP server?
I am trying to find the LEAST intensive solution to allow full access under the newer rasbian version, like I had before stretch... I don't particularly care what WAY/protocol I need to use, so long as it provides the functionality.
- martin
Re: I have the same problem.
When you login with SSH terminal, do you get some prompt after login? (for some additional password maybe?)
Why do you even use SCP? Did you try SFTP?
Why do you even use SCP? Did you try SFTP?
- Krazz
I have the same problem.
And here's the log output...
. 2018-09-12 09:40:37.126 --------------------------------------------------------------------------
. 2018-09-12 09:40:37.127 WinSCP Version 5.13.4 (Version 8731) (OS 10.0.17134 - Windows 10 Enterprise)
. 2018-09-12 09:40:37.127 Configuration: HKCU\Software\Martin Prikryl\WinSCP 2\
. 2018-09-12 09:40:37.127 Log level: Normal
. 2018-09-12 09:40:37.127 Local account: FQF-KRAZZ\krazz
. 2018-09-12 09:40:37.127 Working directory: C:\Program Files (x86)\WinSCP
. 2018-09-12 09:40:37.127 Process ID: 3064
. 2018-09-12 09:40:37.127 Command-line: "C:\Program Files (x86)\WinSCP\WinSCP.exe"
. 2018-09-12 09:40:37.127 Time zone: Current: GMT+2, Standard: GMT+1 (Västeuropa, normaltid), DST: GMT+2 (Västeuropa, sommartid), DST Start: 2018-03-25, DST End: 2018-10-28
. 2018-09-12 09:40:37.127 Login time: den 12 september 2018 09:40:37
. 2018-09-12 09:40:37.127 --------------------------------------------------------------------------
. 2018-09-12 09:40:37.127 Session name: OctoPi (Modified site)
. 2018-09-12 09:40:37.127 Host name: 192.168.20.8 (Port: 22)
. 2018-09-12 09:40:37.127 User name: pi (Password: Yes, Key file: No, Passphrase: No)
. 2018-09-12 09:40:37.127 Tunnel: No
. 2018-09-12 09:40:37.128 Transfer Protocol: SCP
. 2018-09-12 09:40:37.128 Ping type: Off, Ping interval: 30 sec; Timeout: 15 sec
. 2018-09-12 09:40:37.128 Disable Nagle: No
. 2018-09-12 09:40:37.128 Proxy: None
. 2018-09-12 09:40:37.128 Send buffer: 262144
. 2018-09-12 09:40:37.128 SSH protocol version: 2; Compression: No
. 2018-09-12 09:40:37.128 Bypass authentication: No
. 2018-09-12 09:40:37.128 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: Yes
. 2018-09-12 09:40:37.128 GSSAPI: Forwarding: No; Libs: gssapi32,sspi,custom; Custom:
. 2018-09-12 09:40:37.128 Ciphers: aes,chacha20,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2018-09-12 09:40:37.128 KEX: ecdh,dh-gex-sha1,dh-group14-sha1,rsa,WARN,dh-group1-sha1
. 2018-09-12 09:40:37.128 SSH Bugs: Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto
. 2018-09-12 09:40:37.128 Simple channel: Yes
. 2018-09-12 09:40:37.128 Return code variable: Autodetect; Lookup user groups: Auto
. 2018-09-12 09:40:37.128 Shell: sudo su -
. 2018-09-12 09:40:37.128 EOL: LF, UTF: Auto
. 2018-09-12 09:40:37.128 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes; Follow directory symlinks: Yes
. 2018-09-12 09:40:37.128 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2018-09-12 09:40:37.128 Local directory: D:\Private\Minicloud\3D-filer\OctoPI\usr\local\bin, Remote directory: /, Update: Yes, Cache: Yes
. 2018-09-12 09:40:37.128 Cache directory changes: Yes, Permanent: Yes
. 2018-09-12 09:40:37.128 Recycle bin: Delete to: No, Overwritten to: No, Bin path:
. 2018-09-12 09:40:37.128 DST mode: Unix;Timezone offset: 0h 0m
. 2018-09-12 09:40:37.128 --------------------------------------------------------------------------
. 2018-09-12 09:40:37.151 Looking up host "192.168.20.8" for SSH connection
. 2018-09-12 09:40:37.151 Connecting to 192.168.20.8 port 22
. 2018-09-12 09:40:37.152 We claim version: SSH-2.0-WinSCP_release_5.13.4
. 2018-09-12 09:40:37.209 Server version: SSH-2.0-OpenSSH_7.4p1 Raspbian-10+deb9u3
. 2018-09-12 09:40:37.209 Using SSH protocol version 2
. 2018-09-12 09:40:37.209 Have a known host key of type rsa2
. 2018-09-12 09:40:37.213 Doing ECDH key exchange with curve Curve25519 and hash SHA-256
. 2018-09-12 09:40:37.289 Server also has ssh-ed25519/ecdsa-sha2-nistp256 host keys, but we don't know any of them
. 2018-09-12 09:40:37.289 Host key fingerprint is:
. 2018-09-12 09:40:37.289 ssh-rsa 2048 09:aa:82:de:b4:31:35:15:a1:b6:08:f8:a3:7c:f1:4f ke3yLpiJB8MlHFTngjA5NoBm0VLm1meSXbKiJN/zRXM=
. 2018-09-12 09:40:37.329 Host key does not match cached key
. 2018-09-12 09:40:37.329 Host key matches cached key
. 2018-09-12 09:40:37.329 Initialised AES-256 SDCTR client->server encryption
. 2018-09-12 09:40:37.329 Initialised HMAC-SHA-256 client->server MAC algorithm
. 2018-09-12 09:40:37.329 Initialised AES-256 SDCTR server->client encryption
. 2018-09-12 09:40:37.330 Initialised HMAC-SHA-256 server->client MAC algorithm
! 2018-09-12 09:40:37.330 Using username "pi".
. 2018-09-12 09:40:37.343 Server offered these authentication methods: publickey,password
. 2018-09-12 09:40:37.344 Prompt (password, "SSH password", <no instructions>, "&Lösenord:")
. 2018-09-12 09:40:37.344 Using stored password.
. 2018-09-12 09:40:37.356 Sent password
. 2018-09-12 09:40:37.446 Access granted
. 2018-09-12 09:40:37.446 Opening session as main channel
. 2018-09-12 09:40:37.640 Opened main channel
. 2018-09-12 09:40:37.641 Started a shell/command
. 2018-09-12 09:40:37.666 --------------------------------------------------------------------------
. 2018-09-12 09:40:37.666 Using SCP protocol.
. 2018-09-12 09:40:37.666 Doing startup conversation with host.
! 2018-09-12 09:40:37.666 sudo: no tty present and no askpass program specified
. 2018-09-12 09:40:37.680 Skipping host startup message (if any).
> 2018-09-12 09:40:37.680 echo "WinSCP: this is end-of-file:0"
. 2018-09-12 09:40:37.680 Server sent command exit status 1
. 2018-09-12 09:40:37.681 Disconnected: All channels closed
* 2018-09-12 09:40:37.699 (EFatal) **Anslutningen har oväntat avslutats.** Servern skickade kommandot slutstatus 1.
* 2018-09-12 09:40:37.699 Fel uppstod när startmeddelande hoppades över. Ditt skal är antagligen inkompatibelt med applikationen (BASH rekommenderas).
- martin
Re: Connecting to Octopi (0.15.1) and getting shell error
Please attach a full session log file both for Octopi 0.14 and 0.15 (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
- stady234
Connecting to Octopi (0.15.1) and getting shell error
I am getting an error when connecting to the newest version of octopi (0.15.1). I copied the exact setting I used on the previous version (0.14.0) and do not receive any errors.
When I (attempt) connect to the new one i get this:
Here are my settings for all three OCTOPI... again on the two old versions (0.14.0) it works, but the new (0.15.1) fails...
When I (attempt) connect to the new one i get this:
Here are my settings for all three OCTOPI... again on the two old versions (0.14.0) it works, but the new (0.15.1) fails...