Hello again. It appears that for some reason, Companion’s websocket is not running. The websocket is utilized for giving progress updates.
From what I can tell, within the inner workings of Companion, upon an upload, it generates a token and returns that to the client from the /url/get route. From there, the client attempts a connection at /api/<token>. This 404 error is caused by that route not existing for some reason.
What happens if you attempt this with a different provider? Does the issue persist even with a different provider?
From what I can tell, the first part of the token in the route (711afa45) should be the same as the debug output (fda6eba0). For some reason, there’s a token mismatch. What happens if you attempt the upload again?
- Andrew