vscode-remote-release
vscode-remote-release copied to clipboard
[Remote-SSH Bug]: Jailed Shell cPanel user unable to open integrated terminal: The terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.).
Is there an existing issue for this bug?
- [x] I have searched the existing issues
Required Troubleshooting Steps
- [X] I have followed these troubleshooting steps
- [X] I have tried both values of the
remote.SSH.useLocalServersetting
Issue
It connects successfully, files can be edited and saved, but the integrated terminal does not work as expected with "Jailed Access" set to the cPanel account.
Expected Behavior
The expected behavior is for the terminal to open.
If the cPanel is set to "Normal Access" the terminal launches correctly.
Steps To Reproduce
Connect via Remote SSH to cPanel set as "Jailed Shell" SSH Terminal access Open terminal ERROR: The terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.). Terminal automatically closes
Remote-SSH Log
N/A No log available, exception error thrown, terminal closes.
cc @Tyriar @meganrogge for any thoughts
does disabling shell integration, terminal.integrated.shellIntegration.enabled fix it for you?
Hey there,
No, that does not solve the problem.
settings.json { "terminal.integrated.shellIntegration.enabled": false, ... }
Still predictably throws: The terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.). when connected to the account and initiating a terminal in the editor.
Changing the cPanel status to "Normal" shell resolves this, but of course carries more security risks.
On Mon, Jun 3, 2024 at 11:29 AM Megan Rogge @.***> wrote:
does disabling shell integration, terminal.integrated.shellIntegration.enabled fix it for you?
— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-remote-release/issues/9876#issuecomment-2145515161, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTAHIJ3OTKP6IN2P556NATZFSDWNAVCNFSM6AAAAABHSEDKTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGUYTKMJWGE . You are receiving this because you authored the thread.Message ID: @.***>
has this always been the case or has the issue appeared recently?
I was just working on this issue. :)
I believe it wasn't an issue in an earlier version of VSC, but I can't remember what version the issue started.
I was able to find another thread about this that another user was experiencing the same issue: https://stackoverflow.com/questions/70052130/how-to-fix-vs-code-error-with-remote-ssh-the-terminal-process-failed-to-launch
On Fri, Jun 7, 2024 at 2:13 PM Megan Rogge @.***> wrote:
has this always been the case or has the issue appeared recently?
— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-remote-release/issues/9876#issuecomment-2155301735, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTAHIOP5CRPU3EINCKL6ADZGHZ4JAVCNFSM6AAAAABHSEDKTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGMYDCNZTGU . You are receiving this because you authored the thread.Message ID: @.***>
Hey @Tyriar @meganrogge, this issue might need further attention.
@legendarylion, you can help us out by closing this issue if the problem no longer exists, or adding more information.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Team,
The issue still persists. It seems to be a permissions issue with command line and jailed vs normal permissions. Normal works, jailed always fails.
On Mon, Oct 14, 2024 at 8:33 AM vs-code-engineering[bot] < @.***> wrote:
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting https://aka.ms/vscodeissuereporting guidelines.
Happy Coding!
— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-remote-release/issues/9876#issuecomment-2411102198, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTAHIO33JJU7FTHRUYAZKTZ3O2ZVAVCNFSM6AAAAABHSEDKTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJRGEYDEMJZHA . You are receiving this because you were mentioned.Message ID: @.***>
@legendarylion this is the first time I've heard of cpanel and a "jailed shell". Given this error is unique to this cpanel service I recommend reporting it over there as they're doing something that is not compatible with how we create ptys. It looks like it's throwing somewhere in https://github.com/microsoft/node-pty/blob/8bdbd712f40acb939dbab1def8a1c3a815254f74/src/unix/pty.cc#L258, maybe someone from that company can help figure it out and upstream support if it looks reasonable.
Copy that. I'll relay it to the cPanel support teams.
On Tue, Oct 15, 2024 at 10:02 AM Daniel Imms @.***> wrote:
@legendarylion https://github.com/legendarylion this is the first time I've heard of cpanel and a "jailed shell". Given this error is unique to this cpanel service I recommend reporting it over there as they're doing something that is not compatible with how we create ptys. It looks like it's throwing somewhere in https://github.com/microsoft/node-pty/blob/8bdbd712f40acb939dbab1def8a1c3a815254f74/src/unix/pty.cc#L258, maybe someone from that company can help figure it out and upstream support if it looks reasonable.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-remote-release/issues/9876#issuecomment-2414010769, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTAHIPFMONPUIPGUQJ3ZNDZ3UN7JAVCNFSM6AAAAABHSEDKTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGAYTANZWHE . You are receiving this because you were mentioned.Message ID: @.***>