Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iot Edge error configuration has correct URIs for daemon mgmt endpoint - Error SocketError - SocketErrorCode (TimedOut) : Operation timed out #7128

Closed
danudeep90 opened this issue Oct 17, 2023 · 6 comments

Comments

@danudeep90
Copy link

I am trying to deploy custom docker images via Azure Portal. I provided all the registry details and docker image information, but i see that there is some issue with EdgeAgent downloading docker images. On inspecting the logs i can see the message below

image

Also, on running the command sudo iotedge check --verbose i see an error as shown below
image

The error message is
configuration has correct URIs for daemon mgmt endpoint - Error
SocketError - SocketErrorCode (TimedOut) : Operation timed out

@gauravIoTEdge
Copy link
Contributor

@danudeep90 - The key is invalid. Deleting it and trying again would be a simple way to proceed. Could you give that a shot please?

@danudeep90
Copy link
Author

@gauravIoTEdge : I am using symmetric key for authentication. Tried with a new key as well it doesnt work

@gauravIoTEdge
Copy link
Contributor

Please provide detailed repro steps. We need to know exactly what you did to be able to help you and to point out if something may have been missed or done differently.

@gauravIoTEdge
Copy link
Contributor

@danudeep90 - We typically see this error when the hostname has been changed, but that may not be the only reason.

But we can't help you without repro steps. I understand it's not working for you. That's different from it not working at all.

@scout208
Copy link

Hi, I'm getting the same issue. I haven't changed my hostname though. For me it just started happening suddenly. The edge device was working fine a few days ago and now it won't connect.

@gauravIoTEdge
Copy link
Contributor

@scout208 - Please file a new issue with logs and repro steps (or at least an indication of what changed). Help us help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants