Nextcloud 13 - Call for QA!

Feature
22

You did nethforge-testing not nethserver-testing?

1 Like
23

Please execute the following, it should update nethserver-nextcloud…

yum install nethserver-nextcloud --enablerepo=nethserver-testing

1 Like
24

You’re right, thanks a lot.

I did:

yum remove nethserver-nextcloud

and after that:

yum install nethserver-nextcloud --enablerepo=nethserver-testing

Thank you too. Know it works without any problems.

1 Like
25

Error came from wrong gateway setting in NS installation.

Now everything is good:

image

  1. test clean install and update from 12.0.5 => test passed o.k.
  2. verify that admin settings has no warnings or errors => test passed o.k.
  3. verify login as admin and normal user with ad => test passed o.k. (ldap not tested)
  4. verify one nextcloud app installation at least => installed calendar: test passed o.k.

Tested on proxmox VM, clean install from iso 7.4.1708, installed NC 12, updated to NC 13 via testing repo.

Great job @alep . Thanks a lot for your work. :+1: :ok_hand:

2 Likes
26

I tested it on a fresh VM and when installing without Nethserver-testing you get the white/blank screen in firefox. One has to install the nethserver-nextcloud testing package to make Nextcloud 13 work.
@davidep , is this a problem? It may be the same when installing from software center like @flatspin , the nethserver-nextcloud testing package has to be pushed to nethserver-updates I think.

27

Hi, on fresh install from web-gui also have problem (red yum cache problem) and 500 error when entering nextcloud.
Is it a bug that nextcloud 13 is in updates if it needs nethserver-nextcloud testing?
Updating from 12.0.5 to 13 went ok but seems to have same problem as before - AD groups are not respected.
If check “share only in groups” every user in autocompletion is listed, if i turnoff this it not shows any user but i still can share with any user AD ldap and local. Is there any fix for this? Thanks in advance.

28

or maybe is better to move nextcloud13 package in nethserver-testing instead of nethserver-updates?

3 Likes
29

I thought Nextcloud 13 is already tested so is in nethserver-updates. If is not it’s a bad practice to put it there, i think. How we can avoid this is the future?
Nethserver is a great piece of software but i had few problems after update that i thing shouldn’t happen on a server. Is it possible or maybe needed by users to make updates more restricted (more safe)? Cheers and thanks for Your support.

30

definitely yes. nethserver-updates is enabled by default, so with an install of NC through softwarecenter you get a broken NC13 by default!
Not easy to solve for a newcomer. Not good for reputation of NS.

2 Likes
31

@dev_team Could you have a look for it.

32

Holy s***t! I bet it’s my fault, but I don’t have access right now to fix the problem.

@flatspin, you can fix your installation by installing everything with testing repository enabled.

Sorry, I will fix ASAP :frowning:

2 Likes
33

Don’t wory. No problem for me so far. I installed from cmd with updates-repo disabled and got NC 12. Update with testing-repo worked perfect. So I have a working installation NC 13. Also found a solution for cert issue with onlyoffice in NC 13.
Everything is fine for me. :wink:

2 Likes
34

Of course the nextcloud package should have been published in nethserver-testing.
I used the wrong command this morning, the problem should now be fixed.

Mirrors will be in sync in few hours.

3 Likes
35

3 posts were split to a new topic: Nextcloud cryptic usernames

36

And when will NC13 pass from testing to updates repo?

Thanks in advance

37

When it’s ready I guess and it’s tested enough.
Would you mind helping us? So we can shorten this period

1 Like
38

Upgraded our production server, no problems so far.

4 Likes
39

NexCloud talk app looks amazing! Very easy and with good performance. They did an amazing job
The WebUI looks very nice and fast

40

remember to enable the app

image
image.png1901×450 95.3 KB

and to enable this option

image
image.png1032×505 67.8 KB

to see the user list

image

41

Hi Team,

Here are my results of upgrading Nextcloud on our test server.

Our server specs are:
NethServer release 7.4.1708 (Final)
Kernel Release - 3.10.0-693.17.1.el7.x86_64

I have this Nethserver Test Server spun up since I installed my prod server. Both my Test and Prod run a domain and have Nextcloud installed. I’ve been keeping them both in step with updates whereby I’ll update my test serer first and confirm it’s working and then update my Prod server.

My Prod and Test Nethserver are both running Nextcloud 12.05 (latest version from Nethserver).

I’ve issued the following command on my test server:
yum install nethserver-nextcloud --enablerepo=nethserver-testing

Install was successful. I’ve now tried to login to my test server but my login is not working when I use an ID I’ve created in Nethserver. I can see the login screen and I’ve confirmed I’m using the correct login ID and the correct password. I receive an error that says:

Internal Server Error
The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details

Remote Address: 10.232.x.x
Request ID: WqFq72Z2m529x8XCEE5rMgAAAA4

I’ve then logged in with the default admin (Nextcloud) account. I can login with this account but everything is extremely slow (both Chrome and Firefox). In the Settings page (used to be called Admin) I can see in my ldap a ‘Configuration Incorrect’ message.

I’ve looked at the logs and I can see the following:

Error core Error while running background job (OC\ServerNotAvailableException): Lost connection to LDAP server.
Fatal webdav Sabre\DAV\Exception\ServiceUnavailable: OC\ServerNotAvailableException: Lost connection to LDAP server.
Error no app in context OC\ServerNotAvailableException: Lost connection to LDAP server.

Anyone else having issues with upgrading to Nextcloud 13 when on a domain?

Thanks,