Stuck in 'Downloading and Extracting Files...'

[gietpa]

Hi,
When I try to pull to local from getflywheel. It is always in stuck on ‘Downloading and Extracting Files…’ never move to next step. All other sites also are same like that. It has happened few days ago and it was okay before that. I also updated to recent version. But it did not fix
Any solution for that?

[ben.turner]

Hey @gietpa - That sounds like something may have become stuck or corrupted during the Pull process of the Connect job.

You probably should log-into your Flywheel account and see if the support team can help pinpoint what’s going on with the remote site’s infrastructure!

[gietpa]

local-lightning.log (53.0 KB)
Hi, Ben
I attached log history. Can you have a look it what is the issues
Thank you

[ben.turner]

Hey @gietpa – Thanks for that Local log!

I’m seeing a few odd things within this log. The two lines that stand out to me are:

{"thread":"main","class":"FlywheelAPI","requestUrl":"https://app.getflywheel.com/api/v2/local/seats","level":"warn","message":"FetchError: invalid json response body at https://app.getflywheel.com/api/v2/local/seats reason: Unexpected token < in JSON at position 0\n    at %%appPath%%\\node_modules\\node-fetch\\lib\\index.js:272:32\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)","timestamp":"2021-11-10T05:10:07.423Z"}

{"thread":"main","code":"ECONNRESET","level":"error","stack":"Error: tunneling socket could not be established, statusCode=400\n    at ClientRequest.onConnect (%%appPath%%\\node_modules\\tunnel-agent\\index.js:166:19)\n    at Object.onceWrapper (events.js:422:26)\n    at ClientRequest.emit (events.js:315:20)\n    at ClientRequest.EventEmitter.emit (domain.js:467:12)\n    at Socket.socketOnData (_http_client.js:547:11)\n    at Socket.emit (events.js:315:20)\n    at Socket.EventEmitter.emit (domain.js:467:12)\n    at addChunk (internal/streams/readable.js:309:12)\n    at readableAddChunk (internal/streams/readable.js:284:9)\n    at Socket.Readable.push (internal/streams/readable.js:223:10)","message":"tunneling socket could not be established, statusCode=400","timestamp":"2021-11-10T23:55:25.754Z"}

The first one appears to be a temporary infrastructure issue with the Flywheel app ( ie, the FetchError: invalid json response... part)

The second error seems like the computer is having issues maintaining a secure connection to the remote server: Error: tunneling socket could not be established, statusCode=400

I don’t see 400 errors often, so refreshing my mind as to what that is, it appears that for some reason, the server thinks that this request isn’t correctly formed:

400 Bad Request

The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
– 400 Bad Request - HTTP | MDN

Do you have any special connections to the internet for this computer? I’m thinking of something like a VPN, or some sort of custom hotspot? Any security settings that are set on this machine, for example, if this is a work machine, did the IT department install a custom SSL certificate?

One possible thing you can try is to cancel out that pull, and delete the site in Local. From there, disconnect Local from Flywheel and try re-connecting. Maybe this will refresh the connection tokens and everything works?

Either way, if you still have issues, let us know more info about the way this computer connects to the internet and be sure to include an updated version of the Local log for us to review any changes since the last log!