Build push error: tus: failed to create upload, caused by Error: connect ETIMEDOUT x.x.x.x:443, originated from request (method: POST, url: https://xxxx/otto/uploads/files, response code: n/a, response text: n/a, request id: n/a)
First I thought it was because of Install Setting. Then I put the first files there by hand and tried to migrate → same result.
Please help
Seems to be an IT fault, we are working on it. Sorry for the bother.
@TobiWahnKenobi I’ve also started seeing this on a particular deployment between two servers, can you shed any light on what the actual cause/solution was ?
Note that I had done a deployment on both servers about 30 minutes prior without issue on a different solution.
Actually my error is slightly different @kduval have you come across this before?
Build push error: tus: failed to create upload, caused by Error: getaddrinfo ENOTFOUND <>, originated from request (method: POST, url: https://<>/otto/uploads/files, response code: n/a, response text: n/a, request id: n/a)
where <> is the actual server address…
Is your destination server behind a firewall? Or are you running an old version of OttoFMS? it looks like your source server is not connecting to the destination properly. I would try turning off the “Push Build” toggle in OttoDeploy, that should make sure that the source server does not try to initiate connections to the destination server.
-Kyle
I’ll give that a go thanks. The destination server is accessed via a VPN connection which I am connected to and has historically always worked fine. Will let you know how I get on.
A restart of otto service on source server, and turning off that push setting, look to have resolved the issue thanks 
Sorry for the late reply. On my end it was a misconfiguration of the dns routing.