janvonde / check_nextcloud

Monitoring plugin to check the status of nextcloud security scan for a given URL

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Could not get get UUID for given host

Django-BOfH opened this issue · comments

I've updated to the latest version and now I receive this error-message:

/usr/bin/php ./check_nextcloud.php -H nextcloud.nausch.org -u /

WARNING: Could not get get UUID for given host nextcloud.nausch.org/. Aborting.

If I check my site manually at scan.nextcloud.com it works:
https://scan.nextcloud.com/results/71668138-b6a3-46bd-aafc-555c06507cef

any hints or suggestions?

I've tried to reproduce your error, but worked for me with php 5.4.16 and php 7.0.19. Which os and php version has your system?

The error indicates an problem while getting the results from https://scan.nextcloud.com/api/queue. Could you try the following:

curl -H 'Content-type: application/x-www-form-urlencoded' -H 'X-CSRF: true' --data-urlencode url=nextcloud.nausch.org https://scan.nextcloud.com/api/queue

I'm using CentOS 7.3 with PHP Version => 5.4.16
On this host it works:
# curl -H 'Content-type: application/x-www-form-urlencoded' -H 'X-CSRF: true' --data-urlencode url=nextcloud.nausch.org https://scan.nextcloud.com/api/queue
{"uuid":"71668138-b6a3-46bd-aafc-555c06507cef"}

BUT on my production system I have:
I'm using CentOS 7.3 with PHP Version PHP Version => 7.0.19
# curl -H 'Content-type: application/x-www-form-urlencoded' -H 'X-CSRF: true' --data-urlencode url=nextcloud.nausch.org https://scan.nextcloud.com/api/queue
"Too many instances queued."

's still not working

Looks like a Problem with IP / the nextcloud API, but not like a problem with this plugin.

Do the both hosts share the same external IP (eg. NAT) or are they different?

Hmmm, both hosts has different external IPs, as you assumed. But my check worked fine till 17th May:

Mittwoch, Mai 17, 2017
OK
20:27:36
[ 1/5 ] OK: A+ rating for nextcloud.nausch.org, 0 vulnerabilities identified, last scan: 17.05.2017 - 13:43:52h

Since May18th the check is broken. :/ And I've nothing changed like updates or anything else.

Yesterday the problem started to occur at one of our instances. Investigations shows that despite our check_interval of 24h seems great enough, the rate limit is hitting. @janvonde do you know any documentation of the (inofficial API) or time limits?

@nbuchwitz I am sorry but no. I had contact with @LukasReschke via twitter and he told me about the ~250 post limit per day... maybe it is per year?

Do you know, if there is a way to check if a site is rate-limited or blocked?

I've ask Nextclouders via Twitter:

@Nextclouders Your secuity-scanners seems broken. May you fix it? Since 2017-07-22 I can't (re)check sites! :/

The answer:
Replying to @Pirat_Django
we know, sorry about that. Sadly the flood of complains (many automated) has blocked us from scanning... We are looking for a solution.

Is this still broken?

commented

This just occurred on my system. Is there a solution?

same here