Bug Completed
8 comments

Acknowledge function stopped working in v 1.0.3

I seem to have lost the ability to ACK an alert with this update. I do not see any attempts being made in the Nagios server logs.
Dino
Dino
Apr 10, 2026 4:46 PM

Comments (8)

Please log in to add a comment.

Dino
Dino
May 2, 2026 6:36 AM
Actually nothing seems to get actually submitted to the server whatsoever, including downtimes and so on.
rv400
rv400
Jul 10, 2026 1:24 AM
I'll look into it and apply a fix to the next release.
rv400
rv400
Jul 12, 2026 3:19 AM
This issue may be submitting an acknowledgment without a comment. I am releasing a update shortly that should resolve the issue.
rv400
rv400
Jul 14, 2026 10:08 PM
Hi, and thanks for the detailed report — including the note that nothing shows up in the Nagios server logs, which helped us pinpoint this quickly.

You're right: in version 2.0, external commands (acknowledgements, downtimes, and other actions) could silently fail to submit to the server, even though the app appeared to accept them. This was fixed in NagMon 2.0.1, along with a related issue where servers using Digest
authentication would reject command submissions.

Could you update to 2.0.1 from the App Store and try again? After updating, an acknowledgement should appear in your Nagios log (nagios.log) within a few seconds of submitting.

If you're already on 2.0.1 and still seeing this, please let us know:
- Your Nagios Core version and whether the server uses Basic or Digest authentication
- Whether other actions (rescheduling a check, for example) also fail

and we'll dig in further. Sorry for the trouble, and thanks for taking the time to report it!
Dino
Dino
Aug 3, 2026 1:51 PM
I've updated, I'm still not able to submit from the app but I haven't checked the server logs yet. Will report back and copy/paste any messages I see. Thank you for the due diligence! And I love the new features.
Dino
Dino
Aug 3, 2026 1:57 PM
I don't see anything logged on the server, the specific error message in the App:
"Command Failed - the acknowledgement/downtime could not be submitted/scheduled. Please check your connection and try again."

My instance may be non-standard in that my server responds on an FQDN with no '/nagios' subdirectory/alias. I noticed that I need to include '/nagios' in the Path when I add the server, otherwise it will not get added properly. My best guess is that it's related.
Dino
Dino
Aug 3, 2026 2:00 PM
I might have inadvertently found another issue, I'll put in a separate issue for it.

Short description of the unrelated issue: I have two Servers added. One happens to be down at the moment for maintenance. I noticed that the dashboard takes 60 seconds+ to load if one server is offline. Disabling the offline server is an easy workaround but I wonder if any timeouts/retries could be submitted in parallel.
Dino
Dino
Aug 3, 2026 2:13 PM
Here is the log for a command I successfully sent through the web UI:

<redacted.ip> - nagiosadmin [03/Aug/2026:15:11:10 -0400] "POST /nagios/cgi-bin/cmd.cgi HTTP/1.1" 200 1404 "https://<server.fqdn.redacted>/nagios/cgi-bin/cmd.cgi?cmd_typ=3&host=<host.fqdn.redacted>&service=MySQL+Health" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36"