Back for another VS Code setup -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Back for another VS Code setup
From: "Art Tostaine, Jr." <atostaine@xxxxxxxxx>
Date: Fri, 6 Jun 2025 10:25:12 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I can connect with iACS SSH Terminal to my IBM i. VS code fails immediately.

I've placed the key in my home/user/.ssh, added it authorized.keys, code
page 437. I have all authorizations turned on for that file now.

Are there any logs I can look at on IBM i? Copilot offered to analyze my vs
code logs and showed these errors:

-What happened?
The SSH connection was established and you were prompted for a password.
Authentication succeeded, but after the "ready" message, the connection
hung and timed out after about 17 seconds.

I don't think I should be prompted for a password. The customer box is
V7R3. I'm off to check if any PTF's required.

Any suggestions appreciated.

Thank you, Art

Follow-Ups:

RE: Back for another VS Code setup , Sizer, Joseph

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.