Some bugs need to get adressed
Posted: 15 Mar 2022, 06:03
I guess the latest version with the security fixes got some real hard issues. Here is what i saw in only a few minutes while installing
Lets start with installing "Online Mode"
What shall i chose? First or Last ? The First was it..
After installing i began to create the raid...
Well for no reasons the Tos Wizard began again.. and it forced me to so (while it tried to create a raid5).
Okay so lets do the wizard again..
Time was changed to Bejing again (also if i have chosen +1 Berlin in the wizard), okay no problem i changed it.. checked update and the TOS Crashed).
After the restart i was able to change the timezone
So after deadbolt i changed the standard HTTP port to 5050
And saw this
Okay so i went to the Port 5050 and saw this
So okay, http is broken now so i went to https, i changed here the standard port to 5555 and .. saw this here
Off course he didn't changed the port to 5555 (connection refused) it was already the standard port. So i changed it better back in the configuration because HTTP is already broken and if i also loose https i have nothing more.
So lets see what ressources are doing
Fatal Error.
Well some quality management should really look into the TOS to make it more stable in the next update.
Lets start with installing "Online Mode"
What shall i chose? First or Last ? The First was it..
After installing i began to create the raid...
Well for no reasons the Tos Wizard began again.. and it forced me to so (while it tried to create a raid5).
Okay so lets do the wizard again..
Time was changed to Bejing again (also if i have chosen +1 Berlin in the wizard), okay no problem i changed it.. checked update and the TOS Crashed).
After the restart i was able to change the timezone
So after deadbolt i changed the standard HTTP port to 5050
And saw this
Okay so i went to the Port 5050 and saw this
So okay, http is broken now so i went to https, i changed here the standard port to 5555 and .. saw this here
Off course he didn't changed the port to 5555 (connection refused) it was already the standard port. So i changed it better back in the configuration because HTTP is already broken and if i also loose https i have nothing more.
So lets see what ressources are doing
Fatal Error.
Well some quality management should really look into the TOS to make it more stable in the next update.