Setting SERVERPORT has no effect

[elronzo]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Setting the ENV variable SERVERPORT has no effect. Wireguard still listens on port 51280

Expected Behavior

SERVERPORT should provide the ability to set a custom port.

Steps To Reproduce

Set SERVERPORT to some other than the default port and do a wg show in the running container.

Environment

- K3s
- wireguard container running as a K8s pod

CPU architecture

x86-64

Docker creation

not relevant

Container logs

n/a

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

Docker creation details are relevant and an example of the WG conf would be extremely helpful.

[github-actions]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

[Roxedus]

It will still listen to 51280. It will only set the port in the peer file, in the case you port forward 51280 to something else on the outside. It is only used as part of the generation of the endpoint line.

[aptalca]

There are lots of similar closed issues here