Occasionally on restart container, wg conf becomes invalid and cant self resolve

[voc0der]

Generally if I take the containers down and bring them up, this one works fine, but sometimes it finishes the up process with:

2025-03-06 05:36:10,677 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error

Here's is wg0.conf in the broken state after it fails to properly load:

[Interface]
Address = 
PrivateKey = xxxxxxxxxxxxxxxx/YYYY=
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'

[Peer]
PublicKey = 
AllowedIPs = 0.0.0.0/0
Endpoint = us-virginia-pf.privacy.network:1337

This problem has happened a few times over the months and requires me to dummy other values there from a working config before it starts again.

[binhex]

it should resolve as this value is dynamically assigned, does a restart of the container not fix this?

For ref here is the line to the script that assigns the public key:- https://github.com/binhex/arch-int-vpn/blob/9f1d204fecd8bad6162dc200959f9c1b10627a88/run/root/wireguard.sh#L105

[voc0der]

Okay, I did read that code, and what you're saying makes sense. After trying it a bunch of times, in its failed state, it eventually can resolve itself if you docker compose down && docker compose up enough times.. I didn't notice it quickly because a bunch of containers depend on it, and it takes a while to restart the stack.

It's perhaps due to a (me or PIA) intermittent connection issue or an invalid JSON response? https://github.com/binhex/arch-int-vpn/blob/9f1d204fecd8bad6162dc200959f9c1b10627a88/run/root/wireguard.sh#L63

In cases where the config gets to that point and it's invalid, perhaps it should encounter an attempt to retry before giving up? Or maybe it already has that option I'm just doing it wrong.

Maybe adding --retry 5 or something to the curl? but, if the status code is 200 and its feeding whatever, but why would that be the case? ....thinking outloud.

Could also retry loop it based on $(echo "${pia_wireguard_authentication_json}" | jq -r '.peer_ip') right after that.

[ItsOnlyBinary]

I to have hit this issue where its just been in a restart loop with Line unrecognized: PublicKey='` since I updated yesterday, Only noticed today so tried manual restart without success. Then I reverted to 3.0.34-3-06 where it worked fine. Thinking I will get the error so I can create an issue I went back to latest (4.0.0-1-01) and now its not happening anymore (restarted around 3 times turning debugging on/off).