This Bug never got fixed!!!

[OldNerdGuy]

Try renaming your WebAdmin certificate in the released version...


"If the currently used WebAdmin certificate does not use the correct hostname, you can re-generate the certificate here. Just specify the hostname or IP address which is used to access the system, then click Apply."

I have done this on every Beta version, and now in the released version and it does not work. I have posted this many times, but I guess nobody ever saw it.

This came about because I misnamed the installl, and have restored from backup every time. I originally named it proxy1 and tried to rename to proxy1.***.yyy.

Before some wiseacre comes on and says to just to a clean install... sure, that is going to work, but that is not the point. I found a bug, reported it, and it still seems to exist. Also, why should I have to do a clean install when I have it configured how I want it and have good backups. If you were doing a Disaster Recovery, you'd want your backups to work....

I will say the bug I ran across in the configuration wizard, where it kept rejecting my backups, has been fixed. I did the V7 install, and used the wizard to import my 6.933 backup and it worked great. That is progress... Start to finish (from 6.933 to 7.000), the upgrade took only 15 minutes
:-)

[tom]

Originally Posted by OldNerdGuy

This came about because I misnamed the installl, and have restored from backup every time. I originally named it proxy1 and tried to rename to proxy1.***.yyy.

Just for clarification:

The "Basic setup" (first screen where you supply the hostname, admin password etc.) sets up a WebAdmin CA/Cert with the supplied hostname.

After basic setup, re-generating the CA/Cert in "WebAdmin Settings" will not change the hostname in "System Settings".

Vice-versa, changing the hostname in "System Settings" after basic setup does not replace the current WebAdmin CA/Cert.

When you try to re-create the CA/Cert with the hostname it already has, it will silently do nothing ...

[Suppentrulli]

Hi there,

i have reported this bug too, but nobody seems to be interested in it... take a look at [6.933] Can't change webadmin-certificate