You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have deployed atmoz/sftp:latest in an public facing Azure Container App environment and observe this error message continuously in the console logs:
kex_exchange_identification: Connection closed by remote host
Connection closed by 127.0.0.1 port XXXXX
Port numbers range from approx. 30000 - 55000. Monitoring network traffic shows no corresponding rate of connection attempts. Blocking all traffic in the Ingress does not eliminate the message. We do not observe these messages when running the container on a local docker environment.
Is this a known issue? Is there a configuration change we can make to fix the issue?
The text was updated successfully, but these errors were encountered:
It appears this is caused by container health probes, the default is to TCP probe the configured port on the server (22 in this case). We configured custom container health probes to another open port and the noted log messages are gone.
We have deployed atmoz/sftp:latest in an public facing Azure Container App environment and observe this error message continuously in the console logs:
kex_exchange_identification: Connection closed by remote host
Connection closed by 127.0.0.1 port XXXXX
Port numbers range from approx. 30000 - 55000. Monitoring network traffic shows no corresponding rate of connection attempts. Blocking all traffic in the Ingress does not eliminate the message. We do not observe these messages when running the container on a local docker environment.
Is this a known issue? Is there a configuration change we can make to fix the issue?
The text was updated successfully, but these errors were encountered: