updated to last OttoFMS and OttoDeploy
so this is weird if you test the connection before deployment
Well that is strange. Are you using a hostname that the server might not have access to? thats the only reason I can really think this would happen.
No it has a FQDN and a proper SSL, and this copy of OttoDeploy is on that actual server…
TBF it is version next - that might be relevant… In small writing it ays its a 401 error
If its a 401 you might have the wrong API Key in OttoDeploy?
-Kyle