VS Code, WSL, and Authentication cannot be done while running remotely

[Amy Butler]

I’ve experienced the same problem as listed in this initial 2021 question. When VS Code is setup to run with WSL2 Integration Bitbucket Cloud Pull Requests and Jira Issues in VS Code don’t allow authentication while running remotely. I’ve tried the workaround described in the initial 2021 question, however it did not work for me. After those changes I attempted refresh (under Atlassian Settings tab) and reboot (of VS Code GUI), yet neither seemed to change the Atlassian extension settings for localized files (it’s still assuming a remote workspace).

If there’s a way to properly set this up while maintaining WSL2 integration please let me know. Thank you!

‌

[Joris Mak]

I just opened a local window first (so not connected to a remote or to WSL) and opened the atlassian-config page, did the authentication there. When it’s setup there, opening WSL2 projects or on remote servers gives me full functionality.

[Kirk Sutton]

@Joris Mak

thank you. that works for me. can believe it’s so simple

[greenturtle537]

Sorry to be the bearer of bad news, but this issue is still persistent on all netbooks for the time being. Since this extension cannot be installed on the browser-based vs code application, only users with powerful enough computers will be able ever actually authenticate there accounts. Netbook users can only work by connecting to remote machines, codespaces, or equivalent to install the extension, which of course then complains that it can’t be authenticated remotely. While users (me) running Chromebooks or similar will still be able to use a separate browser for Jira/Bitbucket, the RAM limitations of these devices will mostly or entirely destroy a Jira/Bitbucket + VS Code workflow. Any ideas?