Curl installer - Debian

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… :upside_down_face:

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?”
:wink:

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 and here.

Know why? Should I proceed as recommended?

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.

thx again, @geoW

Added both, NC-admin stopped mourning :sweat_smile:

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?

With a bit of luck, it’s just a syntax error in config/config.php . 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/’,
‘mail_domain’ => ‘nextcloudpi.com’,

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

Please, get used to full-size cites as:

prompt>command
output

output
prompt>

Sometimes the lines before the havoc are interesting.

Sure you can ssh to the server and show us

hostnamectl

you could send the output from

sudo ncp-config

→ system → info

or nextcloudpi?

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

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

Examples

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

Yes.

or nextcloudpi?

No.

‘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’,
),

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

‘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’,
),

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

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!

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

@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.

Take a look here:
How to enable SSH using ncp-config or ncp-web
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.

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!