Bug #16360
closedOpenVPN Custom Options Lack Carriage Returns on config.xml Restore
0%
Description
When restoring a config that has OpenVPN custom options, all line items will be "mashed together" on one line without their proper carriage returns for spacing out each line in the custom config.
This can cause issues where a config.xml that is restored from backup will not allow a server or client to start because the custom options are invalid and lacking proper spacing.
For example:
custom-option1
custom-option2
custom-option3
will be presented as follows on a config restore:
custom-option1custom-option2custom-option3
Tested on both 25.07 and 2.8.0, but I don't believe this a new bug exclusive to this version, as I've seen it on previous Plus and CE releases.
Files
Updated by Jim Pingle about 2 months ago
- File clipboard-202508092123-lkio8.png clipboard-202508092123-lkio8.png added
- Status changed from New to Not a Bug
Newlines are not meant to be preserved. You separate statements with a semicolon, not a newline, as it says in the description below that box.
Updated by Alex Kolesnik 14 days ago
Jim, won't this break things if a line contains a comment, like:
custom-option1; # this is for testing option2: custom-option1;
Updated by Jim Pingle 14 days ago
Not if you terminate every line, including the comment line, with a semicolon.