It looks like you've gone offline...

[Chris Curnow]

Extension version: 1.4.3

VS Code: 1.37.1

MacOS: 10.14

‌

I’ve been getting very slow performance from this extension for a few weeks now and this issue might be related.

(For instance it takes nearly a minute to load the list of Jira issues.)

There are several tasks I try where I get the message “It looks like you’ve gone offline.”

I first noticed it when I tried to “Start work on Jira issue” and I’ve been trying several things out for the last couple of hours trying to fix it. But when I try this, I get the message. Just a while ago I was able to get this to work a couple of times but now it has stopped again.

When I tried just now, it came up with this message straight away but when it was working it first came up with the message “getting data” (I think that was the message.)

After a short while, all the fields in the background populate but I can’t do anything because the message is still there.

I have the same issue if I try to:

• Create Jira issue

[Chris Curnow]

This is so incredibly frustrating.

I asked a question in the Community and someone from Atlassian replied with some ideas about where I could get support but they could not get in touch with anyone directly. Apparently the developers of this extension are holed up inside some silo inside Atlassian and no-one can get in touch with them. They operate on their own rules.

It’s also frustrating because this is a brilliant extension and when it works it pretty much does everything I could want it to.

Finally, I just spent a couple of hours trying to fix the issue myself. I completely deleted VS Code and every vscode setting file I could find or even think of. Still no luck.

I was able to get it to work by setting up a separate user account on my machine and making sure there were no globally accessible settings files. So it works. My Atlassian account works. There has to be a settings file somewhere that I haven’t been able to find.

With just the tiniest bit of help from the developers I’m pretty sure I could fix the problem but they are ignoring. I just don’t know why.

[Nick Rundquist]

Chris,

First let me apologize for not responding to you sooner. We failed to coordinate things properly on our end and we'll be making sure that doesn't happen again.

‌

Regarding your initial problem -- We made some changes to how we display connectivity when showing Jira issues in 1.4.3 so it's possible that there's an issue with that. You mention that you're seeing slow performance displaying the list of Jira issues. How many issues are in the list when it eventually shows up?

‌

Regarding where we store data -- We do very little in the way of cacheing actual data so it's probably not relevant to your issue but there are a few places VSCode stores information we write.

On Mac

• Some account details are stored in the system keychain (accessible via Keychain.app).

  • The name of our entries will contain the string atlascode-authinfo.

• Global preferences are in ~/Library/Application\ Support/Code/User/settings.json

  • The keys for preferences related to our extension are prefixed with atlascode.

• Some project specific settings are stored in <project directory>/.vscode/settings.json

  • Again, the keys for our entries will be prefixed with atlascode.

[Chris Curnow]

Hi Nick,

Thanks for getting back to me. I was wondering what was going on. This was very unusual for Atlassian.

Anyway, it is great to be actually talking to someone about it at last.

It is a really weird problem.

Just to let you know about what I have been doing. I

• had this extension working beautifully for several months
• the problems started happening sometime early June
• this past week I have spent quite some time trying to track down the problem
• had already gone through all the settings files you mentioned and couldn’t see anything
• regardless I
  • deleted all the settings files
  • deleted the keychain entry
  • uninstalled the extension
  • completely deleted VS Code (including all the settings and pref files I could find)
  • reinstalled VS Code
  • reinstalled the extension (as the only installed extension)
  • re-authenticated to Jira
  • tried again – same problem
• set up another user account on my Mac
  • did everything I needed to set up the extension
  • it works!!!!
• went back to my original user account (on the Mac)
  • went back to atlassian.nethttp://atlassian.net
  • created another account
  • created a new project in this account with no issues
  • authenticated to this account and project from the extension
  • tried it out – same problem!!!!!!!!

So there must me something somewhere in my user account that is stopping this from working.

Regarding timing,

• in my original user account it took more than 30 seconds to find that there were 0 issues in the new project I setup.
• about the same time for my real project which would have 50 or so issues
• in my new user account it took just a few seconds to populate the list.

I also tried starting in Safe Mode. It was hard to determine how this was going because VS Code does not seem to like working in Safe Mode. It was doing a lot of screen flickering. However the extension did SEEM to be working in Safe Mode.

Is there anything in there that helps you?

Does the extension log anything?

Looking forward to any ideas you might have.

Best regards

Chris

[photo] Chris Curnow Founder & Chief Technical Officer, 4Cast [phone]<tel:+61%20413%20514%20893> | 4cast.com.auhttp://4cast.com.au/ [https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/facebook.png] https://www.facebook.com/4CastPro-1544783052402160/ [https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/linkedin.png] https://www.linkedin.com/in/chris-curnow-9686b8106/ [https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/twitter.png] http://twitter.com/4Cast_au Forecast cost to control - in real time, all the time.

[Nick Rundquist]

Thank you for that, it helps narrow down what might be going on. If you could check and see if any errors are showing up in the logs that would also be helpful.

To enable log viewing for the extension go to the VS Code Settings (cmd-,) and search for “output level” there will be a few results and “Atlassian” should be one of them. If you set the Output Level to “debug” VS Code will start displaying logging events as they happen.

Open the Output panel (View > Output) if it’s not already open. There will be a drop-down menu on the right side that should have “Atlassian” as an option. Selecting that will allow you to see the logging events as they occur.

If you could copy any error messages that show up there it might help us figure out what’s going wrong.

[Chris Curnow]

Ah, thanks. I knew there had to be something like that somewhere.

The output doesn’t give a lot of information though. Here is some output:

I get the first two lines as VS Code starts up.

I get the error lines only occasionally when I try to do something with an issue.

That is, I might click an issue under ‘Open Issues’ and select ‘Start work on Jira Issue’.

I know we WILL get on top of this but it’s a curly one at the moment.

‌

[Chris Curnow]

I just came back to my computer after a break and there were some extra lines in the output:

It would probably be useful if you timestamped these outputs in a future version

[Nick Rundquist]

That makes me wonder a couple of things…

• Did you notice if there’s any correlation between slow performance and the errors in log? (yes, timestamps would help figure that out)
• Do the errors show up immediately after launching VS Code (or opening the project) or is there a gap before they start showing up?
• Does the extension work at all once the errors show up in the logs or does any interaction with Jira fail at that point?

Thank you for your patience.

[Chris Curnow]

Hi Nick,

• No, I haven’t noticed any correlation. It seems slow all the time.
• The first error shows up straight away.
• The lines regarding ‘does not exist…’ showed up when I tried to do something.
• The other lines came up when I wasn’t looking. I just came back to my computer after a while and they were there.
• It seems to keep doing this (online/offline) because I noticed later that there were more lines like these.
• No, I can’t use the extension at all.

Thanks for YOUR help. I really appreciate it.

‌

[Pramod Busam]

@Chris Curnow. Could you try a couple more things?

• Do you use both Jira and Bitbucket features of the extension? If so, could you log in to just one of them and see if you notice any performance improvement?
• Do you have a lot of git repositories open? Or do any of the repositories open in VS Code have a lot of branches (> 100)? If that's the case, could you try cloning a new repository and opening it in VS Code (there is a bug currently which causes performance issues on Create pull request and Start work views if there are a lot of branches).

[Chris Curnow]

Hi Pramod,

• Yes, I have already tried logging out of Bitbucket and only using Jira. Didn’t make any difference unfortunately.
• No, I only have one repository open and it only has a couple of branches
• I just created a new project in Jira and created a new angular project with a very small repo (local only). I tried to create a new Jira Issue in VS Code with the extension and I got the same problem.
• Please note, I set up the same (original) project with the same repo on a different user account on this computer and it worked perfectly. So it has to do with something in my user account. I have tried deleting every file I can think of in my user account but nothing has worked so far.

‌

[Jonathan Doklovic]

@Chris Curnow When you get the “You’ve Gone Offline” message (without getting a subsequent online message) could you simply run these and see if they can connect or give you errors?

‌

curl -I -v http://atlassian.com

curl -I -v https://bitbucket.org

That’s effectively what our offline/online detector does.

[Chris Curnow]

Thanks Jonathon,

After I ran those commands I tried adding a JIra issue. I got this output:

‌

Error: This Jira instance is currently under heavy load and is not able to process your request. Try again in a few seconds. If the problem persists, contact Jira support.

‌

[Chris Curnow]

Sorry, I just realised I didn’t include the output from the commands themselves:

Jira:

chriscurnow$ curl -I -v http://atlassian.com
* Rebuilt URL to: http://atlassian.com/
*   Trying 13.236.8.156...
* TCP_NODELAY set
* Connected to atlassian.com (13.236.8.156) port 80 (#0)
> HEAD / HTTP/1.1
> Host: atlassian.com
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< location: https://atlassian.com/
location: https://atlassian.com/
< date: Tue, 24 Sep 2019 01:42:30 GMT
date: Tue, 24 Sep 2019 01:42:30 GMT
< server: envoy
server: envoy
< transfer-encoding: chunked
transfer-encoding: chunked

< 
* Connection #0 to host atlassian.com left intact

Bitbucket:

‌

chriscurnow$ curl -I -v https://bitbucket.org
* Rebuilt URL to: https://bitbucket.org/
*   Trying 18.205.93.2...
* TCP_NODELAY set
* Connected to bitbucket.org (18.205.93.2) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: businessCategory=Private Organization; jurisdictionCountryName=US; jurisdictionStateOrProvinceName=Delaware; serialNumber=3928449; C=US; ST=California; L=San Francisco; O=Atlassian, Inc.; OU=Bitbucket; CN=bitbucket.org
*  start date: Apr 19 00:00:00 2018 GMT
*  expire date: Apr 21 12:00:00 2020 GMT
*  subjectAltName: host "bitbucket.org" matched cert's "bitbucket.org"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f8081806400)
> HEAD / HTTP/2
> Host: bitbucket.org
> User-Agent: curl/7.54.0
> Accept: */*

‌

[Jonathan Doklovic]

Is that the full Bitbucket output? It doesn’t contain the actual HTTP response code. Just wondering if that was a caopy/paste issue or if it’s a hung connection.

[Chris Curnow]

Sorry, that was a copy/paste error. I noted it yesterday after pasting it and thought I had fixed it at the time but apparently not. I just ran that one again.

‌

chriscurnow$ curl -I -v https://bitbucket.org
* Rebuilt URL to: https://bitbucket.org/
*   Trying 2406:da00:ff00::22c5:2ef4...
* TCP_NODELAY set
*   Trying 18.205.93.0...
* TCP_NODELAY set
* Connected to bitbucket.org (2406:da00:ff00::22c5:2ef4) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: businessCategory=Private Organization; jurisdictionCountryName=US; jurisdictionStateOrProvinceName=Delaware; serialNumber=3928449; C=US; ST=California; L=San Francisco; O=Atlassian, Inc.; OU=Bitbucket; CN=bitbucket.org
*  start date: Apr 19 00:00:00 2018 GMT
*  expire date: Apr 21 12:00:00 2020 GMT
*  subjectAltName: host "bitbucket.org" matched cert's "bitbucket.org"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fb9a6804200)
> HEAD / HTTP/2
> Host: bitbucket.org
> User-Agent: curl/7.54.0
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200 
HTTP/2 200 
< server: nginx
server: nginx
< cache-control: max-age=900
cache-control: max-age=900
< content-type: application/octet-stream
content-type: application/octet-stream
< strict-transport-security: max-age=31536000; includeSubDomains; preload
strict-transport-security: max-age=31536000; includeSubDomains; preload
< date: Wed, 25 Sep 2019 01:14:56 GMT
date: Wed, 25 Sep 2019 01:14:56 GMT
< x-cache-info: cached
x-cache-info: cached
< content-length: 0
content-length: 0

< 
* Connection #0 to host bitbucket.org left intact

‌

[Jonathan Doklovic]

So, you boot up vscode, the Atlassian extension gices you a “You’ve Gone Offline” message and does NOT give you a “You’ve Gone Online” message, then you run the curl commands and they come back successful? Is that correct? Seems like the Atlassian extension should show you an Offline message and not let you do anything until it figures out you’re back online.

Just trying to figure out exactly what’s going on

[Chris Curnow]

Hi Jonathan,

I think that’s pretty much it.

Some things to note:

• this only happens on one user account on my computer (MacBook Pro OS 10.14)
• I set up another user account on the same computer and everything works in that account
• Yes I get the You have gone offline :( message as soon as I boot up VS Code.
• Yes the curl commands come back successful but it is still show You have gone offline :(
• I have never been watching when it happens but the log shows it repeatedly going online and then offline again.
• I have no idea how long it stays online for. Every time I come back to it, it is showing offline.
• Here is the log after about two hours

It has always felt to me that the connection is just very slow and the extension is on the verge of the timeout. Sometimes it checks and it gets a result before time out. But then it checks again and it is the other side of the timeout.

Of course I could be well off track here. Just trying to make sense of it myself.

‌

[Chris Curnow]

I just got a new error in the Atlassian log:

Error: Error checking for new issues Error: request to https://api.atlassian.com/ex/jira/f1c4d566-65b5-4e6c-a7a8-8b58722f0f66/rest//api/2/search?expand=transitions%2CrenderedFields&fields=summary%2Cdescription%2Ccomment%2Cissuetype%2Cparent%2Csubtasks%2Cissuelinks%2Cstatus%2Ccreated%2Creporter%2Cassignee%2Clabels%2Cattachment%2Cstatus%2Cpriority%2Ccomponents%2CfixVersions%2Ccustomfield_10006%2Ccustomfield_10005&jql=project%20%3D%2010903%20AND%20created%20%3E%20%222019-10-02%2015%3A27%22 failed, reason: getaddrinfo ENOTFOUND api.atlassian.com api.atlassian.com:443It might mean something to you guys.

‌

[Jonathan Doklovic]

@Chris Curnow That last error seems like an error looking up dns info. At any rate, I agree with you that it seems like something is taking a long time and my guess is that it’s tying up the main javascript thread which is then causing a lot of weird side-effects.

What’s tying things up is the question. I’m not sure if you use the Bitbucket features or not, but we’ve had some performance issues with the way we were calling some git operations. It could also be that the user account that has the problems has a lot of associated data in Jira and may cause some JQL queries or other requests to take a long time.

That being said, I’m not sure if you’re familiar with the Charles Web Debugger but it let’s you proxy http(s) requests so you can inspect them and see what’s going on with them. We’ve recently released 2.0.0-beta3 of our extension which resolves the git issues and enables you to proxy all of the requests our extension makes through Charles for debugging. It’s not the easiest thing to setup, but if you want to try it out to see if somethings failing or taking a long time, that information would help us debug.

Here goes….

First, you’ll need to download 2.0.0-beta3 and to install it:

Install Instructions:

1. Download the beta version here: https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta3.vsix
2. Within VS Code, click the “Extensions” icon in the App Bar
3. Using the “…” menu in the upper right of the extensions explorer, choose “Install from VSIX…”
4. Find the .vsix file you downloaded in step 1 and choose it for installation
5. After the install is complete you must restart vscode.

After that, you’ll need to install Charles: https://www.charlesproxy.com/download/

After Charles is installed, you’ll need to configure it to handle our extensions https requests. The first thing to do is to save the SSL certificate we’ll need to proxy https connections.

From the charles menu, choose Help > SSL Proxying > Save Charles Root Certificate… and save the files somewhere handy (possibly your home directory)

Next you’ll need to go to the Proxy > Proxy Settings menu and make sure the box that says “Enable transparent HTTP proxying” is checked.

Next, go to Proxy > SSL Proxy Settings and on the SSL Proxying tab, make sure “Enable SSL Proxying” is checked. Also on this screen, you’ll need to add the following domains. (just the hostname, no port needed)

• bitbucket.org
• api.bitbucket.org
• api.atlassian.com
• auth.atlassian.com

Save all of that and charles should be good to go.

No you’ll need to change some configuration for our extension within vscode. Open the command palette and search for “Preferences: Open Settings (UI)”

On the config page, expand the Extensions and click on “Atlassian”. Somewhere within the Atlassian settings you’ll need to find “Enable Charles” and make sure it’s checked. Also, you’ll need to find “Charles Cert Path” and type in the full absolute path of the SSL Certificate we saved from Charles earlier. Finally, make sure the “Charles Debug Only” box in not checked.

With all of that in place, you should be able to see traffic from our extension in Charles.

Please let me know what you find.

‌

Thanks!

‌

• Jonathan

‌

[Chris Curnow]

I tried to send a comment before but it didn’t go through. Let’s try again.

First the good news.

The beta upgrade to the extensions solves a few of my issues. I can now:

• open a Jira issue
• edit the issue and save it
• create a new Jira issue.

However, I can’t start work on Jira issue – I get the message “It looks like you’ve gone offline.”

OK, I’ll send just this much now.

‌

[Chris Curnow]

Oh dear.

Now I can’t authenticate to Jira at all.

I quit from Charles and turned off Enable Charles.

I did have it sort of working for a while.

Charles was reporting there was something wrong with the certificate and I needed to configure my app to trust the certificate.

I thought I had entered the correct path to the certificate. FYI, I had /Users/chriscurnow/charles-ssl-proxying-certificate.pem. I presume that’s correct. That is the location of the certificate.

[Chris Curnow]

I just noticed the notification in VS Code when I try to login to Jira:

‌

[Jonathan Doklovic]

Hi @Chris Curnow ,

Charles is a bit of a pain sometimes. As long as there’s no typo in your path to the cert and the cert can be read by charles it should work. That being said, you may also want to check the SSL proxy settings Root Certificate tab and make sure it’s set to use the auto-generated cert:

Toggling the Enable Charles flag is enough to turn it on/off so after you uncheck it, things should work properly and not proxy through Charles.

Also, I saw the feedback you submitted via the feedback collector and I’m going to put an answer on that ticket, but long story short, I think if we clean up your JQL issues it might help the rest of these.

Finally, the last error you sent (should) happen when you try to authenticate with Jira whens there’s another auth request already in flight that hasn’t completed or timed out yet. All auth requests have a 5 minute timeout.

[Chris Curnow]

Hi Jonathan,

Thanks for your perseverance on this issue.

OK, that info helps.

I’m not sure what was happening with Charles but it seems to be working now. It appears that it is important what order you start things.

The logs in Charles appear to be all OK. There are some entries for api.atlassian.com and they are all good.

I can still list the Jira issues and I can open an issue, edit it and save it without any problems.

The problem occurs when I try to “Start work” on an issue. That’s when I get “It looks like you’ve gone offline.”

But with update to v2.0.0, I’m getting a bit more information in the Atlassian log:

‌

Also a couple of strange things with Bitbucket. Although it told me I had successfully signed into Bitbucket, that’s not showing up in the status bar:

‌

And in the Atlassian extension tab in the sidebar:

‌

[Jonathan Doklovic]

@Chris Curnow OK, it seems to be more of an issue with Bitbucket than Jira. The start work feature actually does a lot of git work because it has the ability to create branches and such.

The error you see in the PR tree usually means you have a project open that either is not a git project, or is a git project but has a remote that’s not pointing to a Bitbucket repo. Can you try opening up a Bitbucket git project in VS Code and try start work again and see if it works. If so, it means we probably need to do better Bitbucket detection in the start work screen.

[Jonathan Doklovic]

@Chris Curnow I think that last error you sent is actually caused by a bug we found. We’ve released version 2.0.1 which corrects it. Could you update to this version, then logout/login to Bitbucket again and retry?

[Jonathan Doklovic]

@Chris Curnow I think the latest 2.0.4 will correct these issues. Can you give it a try?

[Jonathan Doklovic]

@Chris Curnow FYI, we’ve released version 2.1.0 which should help with these issues.

[Chris Curnow]

I will indeed. Sorry, I’ve been pretty busy the last few days.

[Chris Curnow]

You’re new version looks great. Certainly more detail in the log.

I’m getting an error trying to authenticate to Jira. I think it has something to do with the port being in use by my other user account. However I have completely logged out of that account. I probably need to do a restart to clear the port. I’ll do that in the morning. Just FYI, here is the log output:

[2019-10-10 10:55:43:485] Online check attempting to connect to http://atlassian.com
[2019-10-10 10:55:43:485] Online check attempting to connect to https://bitbucket.org
[2019-10-10 10:55:49:204] Atlassian for VS Code upgraded from v2.0.2 to v2.1.0
[2019-10-10 10:55:49:309]  Error: Error getting pipes Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:55:49:309] knownpipes 
[2019-10-10 10:55:49:328] Atlassian for VS Code (v2.1.0) activated in 20 ms
[2019-10-10 10:55:52:529] error refreshing token Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:55:54:010] Online check attempt 1 failed. There are 4 retries left.
[2019-10-10 10:55:56:171] Online check attempting to connect to http://atlassian.com
[2019-10-10 10:55:56:171] Online check attempting to connect to https://bitbucket.org
[2019-10-10 10:56:01:512] Online check connected to https://bitbucket.org
[2019-10-10 10:56:01:513] You have gone online!
[2019-10-10 10:56:05:781] Online check connected to http://atlassian.com
[2019-10-10 10:56:21:636] auth server started on port 31415
[2019-10-10 10:56:33:598]  Error: Error fetching Jira tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:56:33:601] Error authenticating Error authenticating with jiracloud: Error: Error fetching Jira tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:56:58:069] error refreshing token Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:57:04:258]  Error: Error fetching Bitbucket tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:57:04:258] Error authenticating Error authenticating with bbcloud: Error: Error fetching Bitbucket tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:58:01:508] Online check attempting to connect to http://atlassian.com
[2019-10-10 10:58:01:508] Online check attempting to connect to https://bitbucket.org
[2019-10-10 10:58:06:474] Online check connected to https://bitbucket.org
[2019-10-10 10:58:07:563] Online check connected to http://atlassian.com
[2019-10-10 10:58:43:655]  Error: Error fetching Jira tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888
[2019-10-10 10:58:43:656] Error authenticating Error authenticating with jiracloud: Error: Error fetching Jira tokens: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:8888

‌

[Chris Curnow]

No, that wasn’t it. I just remembered I have to disable Charles when I go to authenticate.

With Charles disabled (in vscode) I was able to log in to Jira.

I did get an error message when I went to “Start work” on an issue – “Failed to execute git”. But I think that’s to do with something else I was mucking around with re SSH keys. I will check that out in the morning.

Looking hopeful…

[Jonathan Doklovic]

@Chris Curnow Thanks for the update! You can probably just leave charles disabled since we’re over that hump.

Let me know how it goes!

[Chris Curnow]

Well that was a marathon!!

Yes, it all works now.

Thanks so much for a brilliant product and your tireless efforts to resolve this issue.

[Chris Curnow]

Fixed in 2.1.0

[Jonathan Doklovic]

@Chris Curnow That’s great to hear! It was a long road, but thank you for your patience while we went through this debugging process.

Hope the extension continues to meet your needs.

Thanks!