is it possible that you have maybe an bug in your software, maybe in the auto api privilege mode?
since im using your app my devices are often restarting within 2 hours after mining start - sometimes after 5 mines, sometimes after 10 .. maybe sometimes after 20 minutes or an hour so really random but 99% within the first 2 hours. i've deactivated already auto profit switch and the fail detection features but i was sure that isn't solving this, because if some of this options are triggered i should got an notification too.
so, for now i've shutdown your app und since then my miners are running already over 4 hours without interruption. All Devices are btw Antminer L3+.
Ahh and about Granat:
Was working now again - as you said, the problem seems to be the http instability over the last week. for sure it was checked/enabled, but possibly not reachable Not in your Hands
1) You have configured automatic Antminer API configuration in the in Options dialog, Antminer API Access section. If not configured correctly with IP rules, Awesome Miner will continue to detect the miner as being in restricted mode and will try to reconfigure it every 5 minutes.
2) You have a rule where you configured an SSH action to reboot the Antminer.
Both these two scenarios are indicated with SSH connections and SSH commands in the log file of Awesome Miner (toolbar: Tools -> Log file). Can you please check when a reboot happens if you can see any indication of this?
Hey, my Antminers were now online for about 9 Hours without Awesome Miner. With Awesome Miner, i've got again those restarts so we have to find the Problem at the Software
For sure i have activated automatic antminer api configuration but it is working as it should be. Im connecting via VPN to my Antminers, so i have nothing to do with special Port-Forwardings etc. Awesome Miner is connected to the miners via the remote-vpn network. All Miners are privileged. in the Antminer API Access Tab ive set Hardware to "S7 / L3 / D3" and nothing in IP Address rule (any ip address). root user and password are set and accepted. Im right, that i need this automatic function in case of reboots, right?
i haven't set any custom rules and deactivated already all preconfigured rules.
starpool for next update would be really cool
I can only think of one scenario I've seen in the past where this is going wrong, and that's if you have a temporary network issue where the Antminer fails to respond to the question if it's in Privileged mode. If that fails and Awesome Miner think the miner is running in Restricted mode, you may get a reboot. I can try to address that quite special scenario, but first I would like you to confirm if this is the case.
Im currently not at home so i cant send the log file but it seems that you are right. Ive deactivated the auto. Api configuration since that i got no restarts. Sometimes the vpn responds with 3-5s, which seems to high for the max timeout in your auto. Api configuration function and triggers then the reboot because awesome miner thinks theyre restricted. Its not the problem of an bad connection but the upload stream of the remote vpn isnt really fast 😄 maybe a simple longer timeout would be help or something similar to that.
is it possible to add starpool by myself? i like this pool