<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.E-mailStijl17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=NL link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Recently I followed <a href="https://kb.isc.org/docs/stork-quickstart-guide#debian-apt-compatible">https://kb.isc.org/docs/stork-quickstart-guide#debian-apt-compatible</a> to set up Stork on Debian 13, I ran into two things. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The first thing I ran into has since been added under “Debian 13 differences” after I reported a “command not found” to the customer service. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The other thing is that I keep running into “The machine state was retrieved from the Stork server, but the server had problems communicating with the Stork agent on the machine: Cannot get state of machine”<br><br>As far as I can tell everything that’s supposed to be running is running and I retried the guide on a(nother) Debian 13 install on a different system, only to run into the exact same thing. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Since there’s no firewall active (yet) it can’t be that, so that’s one thing excluded. While settings things up I ran into the identical port issue, got Stork and the agent running on the same system. I changed the config as indicated by the guide under “Stork Server and Stork Agent cohabitating” after which I could register (and later re-register) the agent without problems. Journalctl shows this:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp-ddns[5468]: INFO COMMAND_RECEIVED Received command 'config-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command config-get successfully forwarded to the service d2 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp4[5370]: INFO COMMAND_RECEIVED Received command 'config-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command config-get successfully forwarded to the service dhcp4 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp6[5569]: INFO COMMAND_RECEIVED Received command 'config-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command config-get successfully forwarded to the service dhcp6 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>stork-server[10579]: time="2026-02-08 14:11:34" level="info" msg="Completed pulling DHCP status from Kea apps: 0/0 succeeded" file=" status.go:258 "<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>stork-server[10579]: time="2026-02-08 14:11:35" level="warning" msg="rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: first record does not look like a TLS handshake\"" file=" manager.go:125 " agent="PlrtzGlrb:8080"<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>stork-server[10579]: time="2026-02-08 14:11:35" level="warning" msg="Failed to get state from the Stork agent; the agent is still not responding" file=" grpcli.go:340 " agent="PlrtzGlrb:8080"<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>stork-server[10579]: time="2026-02-08 14:11:35" level="warning" msg="failed to get state from agent PlrtzGlrb:8080: grpc manager is unable to make a call to the agent PlrtzGlrb:8080: rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: first record does not look like a TLS handshake\"" file=" statepuller.go:246 "<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>stork-server[10579]: time="2026-02-08 14:11:35" level="info" msg="Completed pulling information from machines: 1/1 succeeded" file=" statepuller.go:73 "<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO HTTP_CLIENT_REQUEST_AUTHORIZED received HTTP request authorized for 'kea-api'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO COMMAND_RECEIVED Received command 'version-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_RECEIVED command version-get received from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command version-get successfully forwarded to the service d2 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp-ddns[5468]: INFO COMMAND_RECEIVED Received command 'version-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp4[5370]: INFO COMMAND_RECEIVED Received command 'version-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command version-get successfully forwarded to the service dhcp4 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-dhcp6[5569]: INFO COMMAND_RECEIVED Received command 'version-get'<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>kea-ctrl-agent[5805]: INFO CTRL_AGENT_COMMAND_FORWARDED command version-get successfully forwarded to the service dhcp6 from remote address 127.0.0.1<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Since I’m new with Kea DHCP Server and Stork (I’m used to ISC DHCP Server combined with Webmin), I wouldn’t be surprised if I missed a setting, though I would’ve expected that to be in the guide.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Does anyone happen to know why Stork is throwing the error? As for journalctl, Google isn’t giving hits on the TLS handshake error from journalctl in combination with Stork.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>