# Curl installer - Debian

**URL:** <https://help.nextcloud.com/t/curl-installer-debian/126327>\
**Category:** NextcloudPi Documentation\
**Tags:** 1-getting\_started, debian, installation, ncp\
**Created:** [October 30, 2021, 12:14am UTC](https://help.nextcloud.com/t/curl-installer-debian/126327 "2021-10-30T00:14:14Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 10:47am UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/21 "2025-06-17T10:47:31Z")

</div>

thx again @geoW

> You started mourning about the server name practice

Sorry for me being unclear - I didn’t mean to mourn about, but only to ask for the reason of the installer changing the machine name: I didn’t know this behaviour from any other software installer and simply was surprised.

> I renamed all but the mail\_domain

Thx for reporting your experience. With no manual information on this question, this is very valuable information.

> You has been responsible and you will be responsible for your server.

Yea - and it’s good to have some experienced user backing… 🙃

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [June 17, 2025, 11:07am UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/22 "2025-06-17T11:07:06Z")

</div>

> [@FrankBusse](#):
>
> and it’s good to have some experienced user backing… 🙃

> [@FrankBusse](#):
>
> it’s good to have some experienced user

That’s too much, but absolute right with these forums and open software and open speech. it is not one way, we all have learned something today and get smarter, thank you, and I admit, setting up a new server quickly I often wished to be asked:  
“What is the name of your new server?”  
😉

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 11:20am UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/23 "2025-06-17T11:20:25Z")

</div>

After fresh install using the Debian installer (on fresh Debian system), the NC admin page mourns (i.e. warns) about missing UTC hour for maintenance. The parameter `maintenance_window_start` in fact is missing in `config/config.php`. Same with `default_phone_region`.

However, these parameters are set in `config/config.sample.php`, as recommended by the manual [here](https://docs.nextcloud.com/server/31/admin_manual/configuration_server/background_jobs_configuration.html#parameters) and [here](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#default-phone-region).

Know why? Should I proceed _as recommended_?

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [June 17, 2025, 12:53pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/24 "2025-06-17T12:53:55Z")

</div>

> [@FrankBusse](#):
>
> Know why?

In most unattended installations, it seems better to let data unfilled and throw error messages, so the admin can tackle it afterwards than to prefill wrong data, that may damage or throw error messages on other settings, whether that is the case here, I don’t know. Keep on, the maintenance window is an 6h interval, so putting 1 means 01:00 - 07:00.

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 12:57pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/25 "2025-06-17T12:57:41Z")

</div>

thx again, @geoW

> [@geoW](#):
>
> Keep on

Added both, NC-admin stopped mourning 😅

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 1:23pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/26 "2025-06-17T13:23:11Z")

</div>

> [@geoW](#):
>
> I renamed all but the mail\_domain

OK, tried same - after reboot NC-admin yells:

> An exception occured while running the setup check:  
> InvalidArgumentException:  
> URL is missing scheme or host in /var/www/nextcloud/lib/public/SetupCheck/CheckServerResponseTrait.php:154  
> Stack trace:  
> #0 /var/www/nextcloud/lib/public/SetupCheck/CheckServerResponseTrait.php(84): OCA\Settings\SetupChecks\WellKnownUrls-\>normalizeUrl()  
> #1 /var/www/nextcloud/lib/public/SetupCheck/CheckServerResponseTrait.php(116): OCA\Settings\SetupChecks\WellKnownUrls-\>getTestUrls()  
> #2 /var/www/nextcloud/apps/settings/lib/SetupChecks/WellKnownUrls.php(57): OCA\Settings\SetupChecks\WellKnownUrls-\>runRequest()  
> #3 /var/www/nextcloud/lib/private/SetupCheck/SetupCheckManager.php(34): OCA\Settings\SetupChecks\WellKnownUrls-\>run()  
> #4 /var/www/nextcloud/apps/settings/lib/Controller/CheckSetupController.php(134): OC\SetupCheck\SetupCheckManager-\>runAll()  
> #5 /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php(200): OCA\Settings\Controller\CheckSetupController-\>check()  
> #6 /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php(114): OC\AppFramework\Http\Dispatcher-\>executeController()  
> #7 /var/www/nextcloud/lib/private/AppFramework/App.php(161): OC\AppFramework\Http\Dispatcher-\>dispatch()  
> #8 /var/www/nextcloud/lib/private/Route/Router.php(307): OC\AppFramework\App::main()  
> #9 /var/www/nextcloud/lib/base.php(1025): OC\Route\Router-\>match()  
> #10 /var/www/nextcloud/index.php(24): OC::handleRequest()  
> #11 {main}

Any idea?

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [June 17, 2025, 1:29pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/27 "2025-06-17T13:29:36Z")

</div>

With a bit of luck, it’s just a syntax error in `config/config.php` . Check your customisations and undo them first.

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 1:48pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/28 "2025-06-17T13:48:43Z")

</div>

> [@devnull](#):
>
> Check your customisations and undo them first.

done - however, after reboot, user access to NC is blocked for “access by an untrusted domain” (referring to `config/config.php`. And there, some unknown friend partly draws back the customisation to

> 7 =\> ‘nextcloudpi’,  
> 5 =\> ‘nextcloudpi.local’,  
> 8 =\> ‘nextcloudpi.lan’,  
> 3 =\> ‘nextcloud’,  
> 14 =\> ‘nextcloud’,  
> ‘overwrite.cli.url’ =\> ‘[https://nextcloud/’](https://nextcloud/%E2%80%99),  
> ‘mail\_domain’ =\> ‘[nextcloudpi.com](http://nextcloudpi.com)’,

Yes, I’m sure to have changed all above entries back to “nextcloudpi”. This behaviour is repeatable…

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [June 17, 2025, 2:01pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/29 "2025-06-17T14:01:59Z")

</div>

> [@FrankBusse](#):
>
> Any idea?

Please, get used to full-size cites as:

prompt\>command  
output  
…  
output  
prompt\>

Sometimes the lines before the havoc are interesting.

> [@FrankBusse](#):
>
> done - however,

Sure you can ssh to the server and show us

> hostnamectl

you could send the output from

> sudo ncp-config

→ system → info

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [June 17, 2025, 2:11pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/31 "2025-06-17T14:11:51Z")

</div>

> [@FrankBusse](#):
>
> Static hostname: nextcloud

or nextcloudpi?

> [@FrankBusse](#):
>
> 7 =\> ‘nextcloudpi’,  
> 5 =\> ‘nextcloudpi.local’,  
> 8 =\> ‘nextcloudpi.lan’,  
> 3 =\> ‘nextcloud’,  
> 14 =\> ‘nextcloud’,  
> ‘overwrite.cli.url’ =\> ‘[https://nextcloud/’](https://nextcloud/%E2%80%99),  
> ‘mail\_domain’ =\> ‘[nextcloudpi.com](http://nextcloudpi.com)’,

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [June 17, 2025, 2:13pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/32 "2025-06-17T14:13:42Z")

</div>

Not the full list. @FrankBusse post full `config.php` entries e.g.:

```auto
'trusted_domains' => array(
  0 => 'localhost',
  1 => '192.168.x.x',  
  3 => 'nextcloud',
  5 => 'nextcloudpi.local',
  7 => 'nextcloudpi',
  8 => 'nextcloudpi.lan',
  14 => 'nextcloud',
),

```

[Examples](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#examples)

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 2:13pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/33 "2025-06-17T14:13:44Z")

</div>

[quote=“geoW, post:31, topic:126327”]

> [@FrankBusse](#):
>
> Static hostname: nextcloud

Yes.

> or nextcloudpi?

No.

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 2:14pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/34 "2025-06-17T14:14:55Z")

</div>

> [@devnull](#):
>
> full `config.php` entries

> ‘trusted\_domains’ =\>  
> array (  
> 0 =\> ‘localhost’,  
> 7 =\> ‘nextcloudpi’,  
> 5 =\> ‘nextcloudpi.local’,  
> 8 =\> ‘nextcloudpi.lan’,  
> 3 =\> ‘nextcloud’,  
> 11 =\> ‘2001:4dd7:b28a:0:62cf:84ff:febd:dcd’,  
> 1 =\> ‘172.30.2.179’,  
> 14 =\> ‘nextcloud’,  
> ),

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [June 17, 2025, 2:20pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/35 "2025-06-17T14:20:44Z")

</div>

Vielleicht sortieren und doppelte Einträge löschen. Hast du kein Backup als es noch funktionierte?

```auto
‘trusted_domains’ => 
array (
  0 => ‘localhost’,
  1 => ‘172.30.2.179’,
  2 => ‘2001:4dd7:b28a:0:62cf:84ff:febd:dcd’,
  3 => ‘nextcloud’,
  4 => ‘nextcloudpi’,
  5 => ‘nextcloudpi.local’,
  6 => ‘nextcloudpi.lan’,
),

```

---

<div class="post-metadata">

**Author:** ![FrankBusse](https://help.nextcloud.com/letter_avatar/frankbusse/32/6_22734026db12803ebb3e059622ac3534.png) [@FrankBusse](https://help.nextcloud.com/u/FrankBusse)\
**Post date:** [June 17, 2025, 3:28pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/36 "2025-06-17T15:28:35Z")

</div>

> [@devnull](#):
>
> Vielleicht sortieren

Replaced the ‘unsorted’ list generated by the installer with the necessary domains - problem solved

---

<div class="post-metadata">

**Author:** ![linuxrules](https://help.nextcloud.com/letter_avatar/linuxrules/32/6_22734026db12803ebb3e059622ac3534.png) [@linuxrules](https://help.nextcloud.com/u/linuxrules)\
**Post date:** [September 28, 2025, 2:05pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/37 "2025-09-28T14:05:21Z")

</div>

I cannot log in the raspberry pi itself, because it asks “nextcloudpi login: \_” and my login/password is wrong. I can use ssh from my PC and also use the website nextcloud.. So how do I get to know or change the password to log into the raspberry pi itself? Thank you!

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [September 28, 2025, 3:18pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/38 "2025-09-28T15:18:13Z")

</div>

> [@linuxrules](#):
>
> and my login/password is wrong.

As pi user.  
You can configure passwords on webui:4443 or ssh  
`sudo ncp-config`

---

<div class="post-metadata">

**Author:** ![linuxrules](https://help.nextcloud.com/letter_avatar/linuxrules/32/6_22734026db12803ebb3e059622ac3534.png) [@linuxrules](https://help.nextcloud.com/u/linuxrules)\
**Post date:** [September 28, 2025, 4:06pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/39 "2025-09-28T16:06:47Z")

</div>

@geoW Thank you. And a pi user is the same as user “pi”? Via the webui (.local) I have made a user “pi” before your message and not part of the admin group. I don’t know if these users are the same as the -only 1- user I see I can change the credentials for in ncp-config, namely nc-admin? nc-admin has ncp as user and should stay this way, I guess. So where do I change the password of user “pi” so that I can login the raspberry pi directly? Thank you! I cannot find any information about the differences/simularities between webui-users and ncp-config.. Or any explanation about ncp-config.

---

<div class="post-metadata">

**Author:** ![geoW](https://help.nextcloud.com/user_avatar/help.nextcloud.com/geow/32/67506_2.png) [@geoW](https://help.nextcloud.com/u/geoW)\
**Post date:** [September 28, 2025, 4:23pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/40 "2025-09-28T16:23:11Z")

</div>

> [@linuxrules](#):
>
> Or any explanation about ncp-config.

Take a look here:  
[How to enable SSH using ncp-config or ncp-web](https://help.nextcloud.com/t/how-to-enable-ssh-using-ncp-config-or-ncp-web/126317)  
And don’t miss reading the other docs, some may be a little dated but nevertheless worth reading to get a better understanding what nextcloudpi is all about.

Setting up ssh acces you create a user which gets sudoer rights. There is no root user configured.

---

<div class="post-metadata">

**Author:** ![linuxrules](https://help.nextcloud.com/letter_avatar/linuxrules/32/6_22734026db12803ebb3e059622ac3534.png) [@linuxrules](https://help.nextcloud.com/u/linuxrules)\
**Post date:** [September 28, 2025, 4:28pm UTC](https://help.nextcloud.com/t/curl-installer-debian/126327/41 "2025-09-28T16:28:29Z")

</div>

Thank you, but ssh doesn’t seem to be the problem? I can ssh into the raspberry with just fine. The problem is that I cannot login directly into the raspberry pi (PHYSICALLY I mean). None of my credentials work and I cannot find information about it. Thank you!

[Previous page](https://help.nextcloud.com/t/curl-installer-debian/126327.md?page=1)

[Next page](https://help.nextcloud.com/t/curl-installer-debian/126327.md?page=3)
