Trying to set up a VPN server via the new instances method, but I cannot get it to match common names. If I turn on strict matching, I simply cannot connect. If I have strict matching turned off, I can connect, but the connection shows up as UNDEFINED under the client name, and client specific overrides are not applied.
I created a new user name (tethys), crated certificates (tethys was entered as the common name), and am logging in with the user name tethys.
No idea what to troubleshoot... everything seems like it should be set up properly. The same config works fine under legacy.
Ours shows this for all clients since we upgraded to 24.7 as well.
Always has shown the proper common name in prior versions
I noticed this too, when you turn off strict matching the connection works. If strict matching is on, it states in the log that the certificate name doesn't match the username, but they are the same. I have tried to recreate the certificate multiple times, always the same result.
Quote from: spacecase-25 on September 27, 2024, 04:56:13 PMTrying to set up a VPN server via the new instances method, but I cannot get it to match common names. If I turn on strict matching, I simply cannot connect. If I have strict matching turned off, I can connect, but the connection shows up as UNDEFINED under the client name, and client specific overrides are not applied.
I created a new user name (tethys), crated certificates (tethys was entered as the common name), and am logging in with the user name tethys.
No idea what to troubleshoot... everything seems like it should be set up properly. The same config works fine under legacy.
I set up a VPN server using the new instances method, but when I enable strict common name matching, I can't connect, and when I disable it, the client is now UNDEFINED and can't apply the custom configuration. I created a user and certificate with the same name (tethys) but it still doesn't work. Does anyone know how to fix this?