Repository navigation
[BUG] <title> generation of non working peers #404
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
trying to set a list of hostnames in the peer commande.
notpossible to use fqdn, because the interface name can only be alphanum charaters
so trying to trim the fqdn to keep alphanum (includes triming . )
But now the generated name is > 15 characters, which is also not supported
triming excess characters
still not solved, because the conf file are generated prefixed by peer_,
and this filename becomes the interface name
and now i have a mandatory non alphanum character as well as 4 extra chars
Expected Behavior
Other issues aren't linked to this specific container.
But please when the var PEER take a list of names instead f a number,
please dont prefix the generated hostnames by peer_ ,
If you must prefix the folder name , but not the .conf file.
Steps To Reproduce
.
Environment
- OS:
- How docker service was installed:CPU architecture
x86-64
Docker creation
.Container logs
.
Activity
github-actions commentedon Feb 2, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
LinuxServer-CI commentedon Mar 5, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
aptalca commentedon Mar 5, 2026
Yes and no. Yes, only alphanum is supported as peer name due to technical reasons. No, it has nothing to do with interface name. I'd like to make clear that the peer name has no functional significance. It's merely for convenience when one is browsing through the config folder. The default behavior is using an incrementing number for the peers.
That's not true. We don't enforce a character limit for peer names. The OS usually has a very long character limit for file paths.
It does not. The conf files generated for the peers here are not active. They are for your reference. You can rename them or edit them however you like before you move them to your client of choice. Most people copy paste the contents of the file. They are equivalent to the conf files that a vpn provider may give you, which usually has a randomly generated name. You do as you please with it.
I just don't see a valid reason or justification for that request.
I fail to see what the core issue here is. It really looks like this is an xy problem.
LinuxServer-CI commentedon Apr 5, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
LinuxServer-CI commentedon Jul 5, 2026
This issue is locked due to inactivity