NCP 1.50.5 update is released for Nextcloud 24.0.8

NextcloudPi Documentation
, ,
1

Nextcloudpi 1.50.5 is released

  • Debian/Raspbian 11 Bullseye
  • Nextcloud 24.0.8
  • Apache, with HTTP2 enabled
  • PHP 8.1
  • MariaDB 10

See PR #1691 for more details.

The release is tested, but always be prepared to rollback

Where do I download the image?

New Images can be downloaded here, or
Update your instance with ncp-config
Uodate your instance through the webui on port :4443

What is new in NCP 1.50.5

  • Move default location of data directory out of nextcloud directory (partial fix for #1417)
  • ssh: Add option to add ssh user to sudo group
  • Disable root user for login
  • Install various templates on docker container start (improves config persistence)

Fixes

  • Keep old data directory if present (partial fix for #1417)
  • Temporarily move and restore user files during nc-restore (partial fix for #1417)
  • Improve robustness of the setup process for notify_push

Development related notes

  • build-docker.yml: Fix update-test on architectures other than x86
  • Many fixes and improvements for the CICD pipelines
  • Add basic integration test for nc-backup

Nextcloud 25 is still in development for NCP 1.51

See details on pull request #1696

5 Likes
2

I pulled the latest docker image and am now getting an error as follows. Suggested fixes?–

Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

  • core
    • INVALID_HASH
      • core/js/mimetypelist.js
    • EXTRA_FILE
      • core/img/filetypes/dwb.svg
      • core/img/filetypes/drawio.svg

Raw output

Array
(
[core] => Array
(
[INVALID_HASH] => Array
(
[core/js/mimetypelist.js] => Array
(
[expected] => 94195a260a005dac543c3f6aa504f1b28e0078297fe94a4f52f012c16c109f0323eecc9f767d6949f860dfe454625fcaf1dc56f87bb8350975d8f006bbbdf14a
[current] => 7261357dcb345c083894f3905c321b735972045aafa6420ecd748d5a60cd8036a9d6a21e6711eae5a1bccfb53909497e955b2cde70fa412eff184fcd4772a832
)

            )

        [EXTRA_FILE] => Array
            (
                [core/img/filetypes/dwb.svg] => Array
                    (
                        [expected] => 
                        [current] => 43731dd5f17a048112ea5109b40b02ec019b3ee2324385a0f448e3bd2264cb13dc160ab018d893f92f8e2f168fd09009b51578c8c6b97a02a1617c67ac087701
                    )

                [core/img/filetypes/drawio.svg] => Array
                    (
                        [expected] => 
                        [current] => 92e0974cf869bf8ab969c3442dc2b80d55fde36441d22924db74916a06b407520aa2a9dc39336f9157195ebede697ffac0e639360879255ab91932d406e1897d
                    )

            )

    )

)

3

I am a noob, so please be patient.

What does the above quoted section mean?

Up to now I had to use the root user called “pi” to do everything:
a) connect via SSH
b) execute root commands on the shell

Using any other user than pi actually caused issues and I was forced to use “pi”.
See the solution from schoetju here:

On the other side I have read that on a raspi generally it is not advisable to keep a root user called “pi”.

So is there a way to create and use a new root user other than “pi” and disable “pi” afterwards?

4

There is a technical difference between user root and using sudo.

for b) you’ve been using the user pi with sudo command.

Please read Create a new sudo-user & delete Pi user

From NCP 1.50.5 on you can also activate SSH for the the user NCP and enable sudo (with the new checkbox):

5

Thanks.

Just to be sure here is a question about the UI for the SSH entry with the checkbox:
There are five fields there and I wonder what I would need to enter there, as I already have the thing up and running with the user “pi”.

a) active - is already checked and I leave it this way?
b) user - here I assume I enter “ncp” now, (instead of the prefilled “pi”), correct?
c) pass - this would be a new password for the user “ncp” just for SSH, right? That is not the ncp password I use to log into NC?
d) confirm - repeating the same new ncp SSH password, right?
e) Enable sudo - to be checked now

And if that has run fine, then I would use the instructions you linked to and just follow the chapters 5) and 6) to delete the pi user, because the ncp user is already set up, right?
Or would I have to create a new “ncp” user there as well following chapters 1) to 4)?

Basically I wonder how many “ncp”-users need to exist and how many already do. There is the OS, there is Nextclooud and there is SSH I think.

6

EDIT

The implementation to create a user in the web interface seems to have been missed, for now use the ncp user, though this user shouldn’t be used later on as it’s the web admin.

Yes

Yes that’s right

Unless I’m mistaken we will implement a way to create a user there but it isn’t there yet, seems it might have gotten missed

It will change the password for the admin web interface as well atm

Yes, confirm the password you want to use, it will be the one you use for the admin interface as well right now

Yes, make sure this is checked if you want to use sudo (which you probably do)

The article isn’t up-to-date, the pi user has been removed from the RPi OS itself

1 Like
7

hallo ich habe den selben Fehler bein integrity check.
- INVALID_HASH
- core/js/mimetypelist.js
- EXTRA_FILE
- core/img/filetypes/drawio.svg
- core/img/filetypes/dwb.svg
konntest du deinen Fehler beheben und wenn ja wie?