[Question] What is the correct setting for 'overwrite.cli.url'

[mf-in-mun]

Hi,

when I’m running php occ setupchecks there’s an entry

Overwrite CLI URL: The “overwrite.cli.url” option in your config.php is set to “https://srv-nextcloud.my.domain.tld” which is a correct URL. Suggested URL is “http://localhost”

This seemed to be in contrast to the official documentation:

Please make sure to set the value to the URL that your users mainly use to access this Nextcloud.

So, what’s the correct setting for the ‘overwrite.cli.url’ parameter?

Currently I have no errors in the log.

BR SMF

---

System: Homelab, container based, using podman, not the AIO,
Almalinux 9.6, NC 31.07 Alpine FPM, Nginx 1.29, PSQL 17.5, Redis, Talk-Server AIO 2.0.2 on it’s own hardware.

[bb77]

Looks the same on my instance, and I think the issue is that when the setup checks are run via the CLI, they can’t know which URL is actually being used by browsers or client apps, so they just default to https://localhost. In my opinion, it doesn’t really make sense to include this part in the CLI output, unless there were a way to explicitly pass the actual URL when running the command.

@mf-in-mun

So, what’s the correct setting for the ‘overwrite.cli.url’ parameter?

The URL you mainly use, i.e. the one you have already configured.

Or in short: I’d say it’s OK as it is.

[wwe]

@bb77

default to https://localhost

this is wrong - https:://localhost will never work (by default).

• http://localhost should work in many cases like bare-metal and similar installations were cron jobs run in the same context as the main app process. in docker installations if you run separate cron container localhost in not the same in cron context.
• https://cloud.domain could be demanding for installations behind reverse proxy.

at the end your server should be able to connect with the address from the CLI. as long you can run curl https://cloud.domain/status.php from your server/container CLI and your cron jobs execute successfully - don’t worry everything

[bb77]

I may not have been clear enough, or perhaps I chose the wrong words.

I didn’t mean to suggest that the OP should use http://localhost, and OP doesn’t do so. However, occ setupchecks does suggest exactly that:

@mf-in-mun

Overwrite CLI URL: The “overwrite.cli.url” option in your config.php is set to “https://srv-nextcloud.my.domain.tld” which is a correct URL. Suggested URL is “http://localhost”

I assume this is because the checks access Nextcloud via http://localhost when run from the CLI, which brings me to the conclussion that this particular check, and the corresponding message, only really make sense when accessing Nextcloud via a browser, because the occ setupcecks command doesn’t allow you to specify the actual URL you’d normally use.

So, it always uses http://localhost, and that’s what ends up being suggested in the output. But as you pointed out, you shouldn’t actually follow that suggestion, and the OP didn’t, but they understandably got confused, since their correct configuration appeared to be flagged as possibly incorrect.

EDIT:

Ah, now I get it. it’s actually http://localhost, and I accidentally wrote https.

Either way, I think this check, at least the part where it suggests another URL, should be omitted when running the setup checks from the CLI, since it only makes sense in the context of a browser where you’re accessing Nextcloud using your actual URL.