I think that core 187 re-introduced an old error that was fixed but now seems to be back. When save an attempt at an ipsec connection you get a ‘Internal Server Error’ When go back in and edit the connection, correct values appear in the wrong fields. No choice but to delete the connection and try again, but get same error… This was a problem previously and I think there was some kind of coding error that was then fixed. Can’t find that old topic no though
When you get the Internal Server Error then go and look in the
/var/log/httpd/error_log
At the end of the file with the most recent messages it will give an indication of where in the ipsec cgi code the failure happened.
I suspect what you are encountering is https://bugzilla.ipfire.org/show_bug.cgi?id=13029
However this bug has not yet had a fix released. I have created a fix and the patch for that is being reviewed and should be able to end up in CU189.
If this is your issue then it means that you are using a PSK and you have a comma in your IPSec secret. As the config elements, including the secret, are stored in a csv file then a comma in the secret means that after it everything is in the wrong place.
Currently the workaround is still to not use a comma in the PSK, as it mentions in the wiki.
If the problem is not related to having a comma in the PSK, or you are not using a PSK but certs then the info from the error_log is needed to figure out what the problem is.
Yes, as soon as I replaced a single quote (in the PSK) with a different character things worked again. I am so sorry to have bothered you with this trivial problem. I was hoping someone would remember the prior incident and solution. Didn’t know it was in the wiki. I should have looked there first. I very much appreciate your taking the time to enlighten my on the solution. I will make a note somewhere to help me remember in the future. jps