In the deployment section, I selected the correct build and files, and ensured that “Push Build to Destination” is turned off. However, when I test the server connections, I receive the following error:
“Source to destination connection failed. Turn off ‘Push Build’ from this source server to run this deployment.”
The error appears to be related to the source-to-destination connection. When I hover over the warning, it says:
“The other server could not be reached. TypeError: fetch failed.”
Despite this error, I’m still able to schedule deployments, and they run successfully.
I’m both curious and concerned about what’s causing this issue. I’ve double-checked all connections and tokens, and everything seems fine.
I’d appreciate any guidance or insight into what might be triggering this error.
The connection that is failing is from the source to destination. Does your destination server have a firewall or any other sort of network protection that prevents the source server from connecting to it? It is not necessarily a problem from OttoFMS’s point of view that these cannot connect since you can turn off the “Push Build” and all network requests come from the destination to the source server.
Hi @kduval,
Thanks for your response. As far as I know, the destination does not have a firewall.
I was able to schedule a deployment and it ran successfully, but the error message hasn’t disappeared. I looked through the documentation to find which endpoint Otto uses, but I couldn’t find anything.
I’m not sure if this is just a bug or if something is actually misconfigured. I haven’t been able to identify the source of the issue.
OttoDeploy is using the “Can reach Other Server” endpoint in the Misc section of the OttoFMS Developer API. it calls to your source server, which then makes a call to the destination server to test the connection. The error message was made more helpful for this endpoint in version 4.11.0, so if your source server is not on 4.11.0 or 4.11.1 I would recommend upgrading and it should give you a more useful error back.