MinimServer website not reachable

[Mangar]

Hello!

I have a QNAP TS-453 Pro and just updated to Version 2.2. After updating to the newest QNAP version and several reboots, the website isn't reachable. I also stopped and started the MinimServer service serveral times, but the website http://qnap:9790 (the hostname of my QNAP is qnap) isn't reachable.

The QuLog event manager also logged "Started MinimServer".

[simoncn]

It sounds like MinimServer might have stopped abnormally after being started. QNAP QTS does not detect this but continues to show a "running" icon for MinimServer.

To check this, use File Station to look at the minimserver.log file in the MinimServer shared folder. Does this file show any error messages?

[Mangar]

Hello Simon,

in this log I found this entry:

minimserver-out.log
~-~
MinimServer: incorrect value for property '.autoUpdate'
MinimServer: startup error

I put a 1 into the field AutoUpdate. I removed it from the config and startet the service twice. Now it's running.

Thank you for your help!

But another question: Where is the new property tab? I can't find it.
https://i.imgur.com/qw15Rax.png

[simoncn]

The problem with the missing Properties tab is causing by a browser caching issue from pages loaded by your previous version of MinimServer. You should be able to fix it by clearing browser cache enties for your local instance of MinimServer.

The correct values for .autoUpdate are true, false and empty. Entering an incorrect value such as 1 should not be allowed and I will fix this in the next update. Thanks for letting me know about this problem.

[Mangar]

(31-12-2022 15:14)simoncn Wrote:  The problem with the missing Properties tab is causing by a browser caching issue from pages loaded by your previous version of MinimServer. You should be able to fix it by clearing browser cache enties for your local instance of MinimServer.

The correct values for .autoUpdate are true, false and empty. Entering an incorrect value such as 1 should not be allowed and I will fix this in the next update. Thanks for letting me know about this problem.

Thank you, now everything is ok.

[simoncn]

In MinimServer update 233, I have added checking so that an attempt by the user to set an incorrect value for .autoUpdate will produce an error message and not allow the setting.

I have also fixed the problem of MinimServer failing to start when .autoUpdate is set to an incorrect value. This could happen if the user edits an incorrect value into a .profile file. If this happens, MinimServer will start and show an error message.

[tarnkappe]

In the release notes the headline says update 232 instead 233…

[simoncn]

Thanks for this, now fixed.