mikeboss Posted March 29, 2019 Report Share Posted March 29, 2019 soll ich fehler betreffend 62.1 ueberhaupt melden? frische installation von 62.1 (mittels angepasstem install-debian.sh) auf debian64 lizenz installiert wenn ich in der web GUI das admin passwort anpasse und speichere greift die einstellung nicht. mit dem neu konfigurierten passwort kann man sich hinterher nicht anmelden, ohne passwort hingegen schon. fehler tritt auf release 62.0 (erneut frisch installiert auf debian64) nicht auf. Quote Link to comment Share on other sites More sharing options...
Support Posted March 29, 2019 Report Share Posted March 29, 2019 Hi, Please upgrade to 62.1 once again. The latest version should be from Mar 27 2019 17:08:26 or around this, and give this a try again. Quote Link to comment Share on other sites More sharing options...
mikeboss Posted March 29, 2019 Author Report Share Posted March 29, 2019 isn't the version downloaded during install the same as the one from the update? I installed 62.1 without updating it, this was today in the morning (march 29th). Quote Link to comment Share on other sites More sharing options...
mikeboss Posted March 29, 2019 Author Report Share Posted March 29, 2019 okay, I tried it again (on a virtual machine this time). freshly installed debian stretch 64 bit. edited "install-debian.sh" so it'll download release 62.1 and installed it according to the manual. login to the web GUI, set a new password for the PBX, logged out -> unable to login with the new password, logging in without password is still possible. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 29, 2019 Report Share Posted March 29, 2019 Well while we are trying to keep Chrome from filling out password that it should not fill out, obviously a few areas went over board. At least the admin password seems to save again... Hopefully we can close this chapter soon. Sorry 62.1 is still "beta". Quote Link to comment Share on other sites More sharing options...
mikeboss Posted March 30, 2019 Author Report Share Posted March 30, 2019 I can confirm that this is fixed (release 62.1 build date Mar 29 2019 15:49:34) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.