Information and Support

Attempting a new setup, I had to create the starter.sh script by hand, and did chmod +x it. The log in /tmp/log_starter.txt keeps showing:

Downloading the OTM binary.
Download failed. Retrying...

Looking at line 103 of starter.sh, I noted

CURL_CMD="curl --silent --connect-timeout 15 --max-time 30 --request POST https://www.foxymon.com/receiver/receiver2.php"

I attempted this in my windows browser, authenticated, and then was met with a completely blank page even in the dev console.

Is there something I should update in the script to point to a site that hosts the binary?

I would like some account cleanup assistance, I cannot figure out if I can do this myself.

Can we please remove 131116 and 131117? I will no longer be using windows clients.

Can we move the one I already paid for which I believe 131116's payment up to 131123?

Can we Nickname as the following

131123 - Inside router
131124 - Outside Router

Once this is sorted, I'll up the second agent to get them both sorted.

Thank you.

Thank you for the assist in regards to all of this. We are sorted and closed. :)

This is for both 131123 and 131124, I have them setup to track my provider in two separate ways, allow me to explain.

131123 - Is on a Pi that's plugged into my home router, it shows repeated "Internal" alerts even though my home network is fine to the point to where I use an app to control my second machine from my first to share keyboard and mouse and it never has an issue. Almost all alerts show internal.

131124 - Is on a Pi with wireless connection straight to my ISPs modem. There is no internal to go down here, this is when the modem stops serving internet access, but I confirm with my third machine that the wireless itself stays functional, it has no route at the times denoted.

The time windows of outages are fairly close as you can see, but that makes that internal flag even more confusing if one agent hard wired behind a router and a wifi straight to modem with no home networking at all are showing the same outage windows.

Can you please check both agent logs and investigate why it is flagging things the way it is? 131124 is most confusing when there's nothing to go down but the modem.