-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After update to 1.3.2 server becomes inaccessible after a time #176
Comments
Thanks for reporting this issue! To help us better understand and troubleshoot the problem, could you clarify a few things? Are you saying you can’t access ZimaOS remotely, or are both local network (LAN) and remote access affected? Also, when you mentioned the reset button, which one are you referring to—is it a software reset option or a physical button on the device? Additionally, have you tried rebooting the machine, and if so, how often does this issue occur? Lastly, could you let us know which version you were using before the upgrade? These details will really help us narrow down the cause. Looking forward to your response! |
Hello, both are inaccessible. The physical power and reset button on the case. I noticed a variation between 4 and 8 hours for the problem to appear. I was on version 1.3.1-1. After updating to 1.3.2-1 the problem seemed to have been resolved, but I needed to change my storage HDs and the problem returned, it is important to note that the OS is on a separate NVME, this has not been modified. |
I am afraid that I also face the same issue. random intervals (sometimes after 1-2 weeks, or during the night). the ZIMACUBE is unreachable via the network and the screen is frozen when I plug in a monitor (cannot type anything). it is not an overheating issue since I have stable temps (even at max load). cannot really tell what is causing this but it also started occurring after update 1.3.2. |
After updating to version 1.3.2, the server becomes inaccessible from both the local and external networks after some time of use. To restore functionality, I need to press the reset button on the case.
The text was updated successfully, but these errors were encountered: