Skip to content

Conversation

@come-nc
Copy link
Contributor

@come-nc come-nc commented Sep 26, 2025

  • Resolves: #

Summary

Current version does a GET on our website, which is heavier than needed, both for our website and the Nextcloud instances.
Changed to a dedicated service and a HEAD request.
Also took the opportunity to remove startpage and correct edri url to avoid a redirection.

Checklist

Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
…redirection

Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
@come-nc come-nc added this to the Nextcloud 33 milestone Sep 26, 2025
@come-nc come-nc self-assigned this Sep 26, 2025
@come-nc come-nc added the 3. to review Waiting for reviews label Sep 26, 2025
@come-nc come-nc marked this pull request as ready for review September 26, 2025 15:13
@come-nc come-nc requested a review from a team as a code owner September 26, 2025 15:13
@come-nc come-nc requested review from nfebe and removed request for a team September 26, 2025 15:13
@Altahrim
Copy link
Collaborator

@Altahrim Altahrim added the pending documentation This pull request needs an associated documentation update label Sep 26, 2025
@Altahrim
Copy link
Collaborator

Need to update https://docs.nextcloud.com/server/latest/admin_manual/installation/harden_server.html#connections-to-remote-servers

Copy link
Member

@joshtrichards joshtrichards left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call.

Maybe add the shuffle just for kicks.

Kind of tempting to put something like https://one.one.one.one/ and/or https://www.speedtest.net/ in here...

'https://connectivity.nextcloud.com', 'https://www.eff.org', 'https://edri.org'
]);

foreach ($siteArray as $site) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
foreach ($siteArray as $site) {
shuffle($siteArray);
foreach ($siteArray as $site) {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we prefer to default to the same one always and avoid random behavior.

@joshtrichards
Copy link
Member

Might be worth backporting this. It's a quasi-bug fix. It's not really a feature exactly.

@come-nc come-nc merged commit 407cc43 into master Sep 28, 2025
202 checks passed
@come-nc come-nc deleted the fix/improve-connectivity-check branch September 28, 2025 12:51
@come-nc
Copy link
Contributor Author

come-nc commented Sep 28, 2025

Documented in nextcloud/documentation#13719
I think we cannot backport because it would require changing firewall configuration on a minor update.

Anyone in a hurry can just set connectivity.nextcloud.com in the config file at connectivity_check_domains.

@nextcloud-bot nextcloud-bot mentioned this pull request Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews enhancement feature: settings pending documentation This pull request needs an associated documentation update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants