[Bug]: .mjs files : Nextcloud should not force admins to modify a working configuration about server

[susnux]

It is a setup check, so it tries to check if you have configured your infrastructure correctly to help you with finding issues.
If you set up your infrastructure in a way Nextcloud can not perform this health checks (either by a faulty DNS setup or a firewall rule), then it is up to you to ignore it.

Meaning:
This is only a warning because we can not help you checking your installation, it is not an error.
If you think it is ok for your usecase, then simply ignore the warning, that what it is for.

So, if I understand well, my Nextcloud instances want me to modify a working configuration, only to suppress some warning messages. Which is, for me, not normal.

What would be the alternative? Silently ignore it?
The test has three possible outcomes:

1. Success -> Test could run and was successful -> Admin does not need to check anything
2. Error -> Test could run and failed -> Admin needs to fix the setup
3. Warning -> Test could not run. This means either it is broken or not but we need to warn the admin that they need to validate it manually that everything is working.

[canoine]

It is a setup check, so it tries to check if you have configured your infrastructure correctly to help you with finding issues. If you set up your infrastructure in a way Nextcloud can not perform this health checks (either by a faulty DNS setup or a firewall rule), then it is up to you to ignore it.

A good tutorial is better than a bad check.

Meaning: This is only a warning because we can not help you checking your installation, it is not an error. If you think it is ok for your usecase, then simply ignore the warning, that what it is for.

Not easy to ignore :

I precise that all the warnings shown here are useless, as this instance does work as expected.

What would be the alternative? Silently ignore it?

Why not. As already said, a good tutorial is better than a bad check.