restarting container breaks server access
Closed this issue · 7 comments
Everytime I restart the container something breaks and I can't access the server unless I claim a new agent.
Sorry to hear this. Can you please tell me how you deployed the container and what exactly breaks?
This is on unraid through the apps tab. On startup I get this error:
2024-08-01T05:09:38.450752Z ERROR playit_agent_core::api::http_client: failed to parse json:
<title>500 Internal Server Error</title>500 Internal Server Error
nginx/1.24.0 (Ubuntu)
2024-08-01T05:09:38.450761Z ERROR playit_agent_core::api::http_client: API call failed error=ParseError(Error("expected value", line: 1, column: 1), 500, "\r\n<title>500 Internal Server Error</title>\r\n\r\n
500 Internal Server Error
\r\nnginx/1.24.0 (Ubuntu)\r\n\r\n\r\n") request=playit_agent_core::api::api::ReqAgentsRundata
2024-08-01T05:09:38.450780Z INFO playit_cli::ui: Got Error
I'm not sure how to explain it more. Let me know what I can do to help.
It is running, but not tunneling to the server. Here's some more logs after the error:
2024-08-01T05:20:56.718667Z INFO playit_agent_core::tunnel::udp_tunnel: send udp session token token_len=68 tunnel_addr=xxx.xx.xxx.x:xxxx
2024-08-01T05:20:56.753233Z INFO playit_agent_core::tunnel::udp_tunnel: udp session confirmed token_len=68 tunnel_addr=xxx.xx.xxx.x:xxxx
2024-08-01T05:20:57.566073Z INFO playit_cli::ui: playit (v0.15.13): 1722489657566 tunnel running, 2 tunnels registered
2024-08-01T05:21:00.647800Z INFO playit_cli::ui: playit (v0.15.13): 1722489660647 tunnel running, 2 tunnels registered
2024-08-01T05:21:03.001972Z INFO playit_agent_core::tunnel::simple_tunnel: update udp channel details details=UdpChannelDetails { tunnel_addr: xxx.xx.xxx.x:xxxx, token:xxxxxxxxxxxxxxxxxxxxx
I'm not sure what I did, but maybe removing the old secret key file helped? I've reinstalled this a few times to get a new claim, but now everything seems to work fine after restarting. Part of the frustration can be attributed to crafty changing my server ip after updating, I'm sorry for any time wasted, but I really appreciate the quick reply. The only reason I came here is because this has happened a few times before.
Hey, thanks for letting me know that you fixed it. No worries. I have one question: did you upgrade from an older version to a new version when this happened?
I can't rule that out completely, but I remember this happening at least two times in the last month. I believe I started using this docker container around the 11th of July so definitely after the latest update.
Okay, thanks for the info, but it's likely that this issue has to do with Playit itself.