Nextcloud Security Scan broken since weeks
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Summary:
Nextcloud Security Scan broken since weeks
Steps to Reproduce:
- Navigate to https://scan.nextcloud.com
- Enter the domain of your Nextcloud instance
- Click the Scan button
Expected Results:
See the last cached security report of that instance with a button to rescan for updating the report.
Actual Results:
Page always displays “Host not found” indicating a DNS issue on the scanning server.
Regression:
This did work fine a few weeks ago.
Notes:
I've tried with multiple of the several Nextcloud instances I admin. All of them actually get scanned but the Scan server always returns “Host not found”.
I was instructedx to report the issue here by the official Nextcloud account on Mastodon. Reference link:
https://mastodon.xyz/@nextcloud/114875147964785331
Version Information:
Does not apply. It's independent of the Nextcloud Server. This problem applies to the SCAN server, not any Nextcloud instance. (See Notes.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at https://scan.nextcloud.com and reproduce the scan with one of the affected Nextcloud instance domains. Investigate why the scanning server reports “Host not found” despite completing scans; done means cached reports display correctly and rescanning updates them.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100