Uploaded artifact and created a deployment prior to any devices being registered.
Deployment status is “queued to start”, as it is waiting for a device.
Connected a device and it registers as pending. Approved the device.
There is now a connected device.
The deployment is still queued and not downloading.
SSH’d into the mender server and tried to telnet to port 9000 and receive:
telnet: could not resolve 127.0.0.1:9000/telnet: Name or service not known
Is there a way to tell if the storage proxy is running?
Also, if there’s a log on the Mender server that I could look into that would be great.
FWIW, on the device, the log reports no problems. It’s just happily checking for updates, checking inventory, etc. No sign of an inability to download the deployment…it’s just not doing it.
How did you create a deployment in the first place without adding any devices to the deployment first? (Unless you are using some of the enterprise features for matching devices?)
I did create a deployment with the a device connected. It still doesn’t update but now I am getting logs on the device. From the log I am guessing that our reverse proxy is misconfigured and routing port 9000 to some other port, either 443 this machine or another, as the logs contains complaining about an invalid character “<” in the response.
Please allow me to investigate this and update before anyone spends any more time on this. Thx.
Hmm. I wonder if something is not happy re the supported crypto protocols, versions, etc between the reverse proxy and the storage proxy? I see posts across the web for similar errors that suggest adding --secure-protocol=TLSv1 to the wget options. But to be honest I’m just reading what others have written and don’t understand it.
Waiting for a confirmation… We may not have opened port 9000 on our firewall when we opened it on the reverse proxy. I’ll confirm and close this thread if that turns out to be the case.