I have a hosted NC at Ionos. Iām using a local CLI client.
Nextcloud Client version
3.16.7-1~deb13u1 (Debian built)
Nextcloud Server version (e.g., 29.x.x):
31.0.6 Enterprise
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Provider
Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Debian Trixie CLI client reports this in the logs
[ warning nextcloud.sync.configfile ]: Default update channel is āstableā because that is the desktop enterprise channel returned by the server.
cfg file only contains this:
config/Nextcloud/nextcloud.cfg
[General]
serverHasValidSubscription=true
I can see in the code where this originates but I donāt understand why there is a warning, or what I can do to prevent it as it seems unnecessary?
QString ConfigFile::defaultUpdateChannel() const
{
const auto isBranded = Theme::instance()->isBranded();
if (serverHasValidSubscription() && !isBranded) {
if (const auto serverChannel = desktopEnterpriseChannel();
validUpdateChannels().contains(serverChannel)) {
qCWarning(lcConfigFile()) << "Default update channel is" << serverChannel << "because that is the desktop enterprise channel returned by the server.";
return serverChannel;
}
}
Any suggestions appreciated - there is a distinct lack of docs on some of the more obscure settings
The warning itself is harmless. What it says is: your Nextcloud server has a valid enterprise subscription and instructed the desktop client to use the āstableā update channel ā which is exactly what the client is now doing. The message is purely informational and arguably should have been logged at DEBUG level rather than WARNING. Nothing needs to be changed on your end.
That said: you are running Nextcloud 31.0.6 Enterprise. Nextcloud 31 is end-of-life for the community edition ā the only reason it is still receiving updates is because IONOS holds an enterprise license that provides long-term support. This means your setup is entirely in enterprise territory, and any questions related to its configuration should go through IONOS support, who as an enterprise customer can escalate directly to Nextcloud if needed. The community forum has no insight into enterprise-specific configurations and is not the right place for these.
I think the warning is because enterprise subscriptions can have their own branded desktop client (with their own rollout/update logic). If you are admin of such a enterprise setup, it is helpful to know that a specific user has community version of the client, so a warning might be a good idea.
Indeed. It should be either information or debug. It is not an error. So it is a bug.
I have been trying to script a log check for warnings and errors, but it keeps getting tripped by this which is a false positive.
Yup I can code around it of course, but it shouldnāt happen.
I am, but it wonāt make any real difference as the bug still exists on this client version, and following versions. Iāll open a new issue thanks.
The only thing that makes it āenterprise specificā is if you have an enterprise subscription. But is actually a bug in the client, not the server, as per the code above.
As above it should be either informational or debug. Nothing ābreaksā so a āwarningā isnāt necessary (IMHO).
As it is I get an unnecessary flag for having a paid version
A warning does not mean something is broken right now.
And for enterprise users that have their own client, then having one user with the community client instead of the custom desktop client, might be a problem. E.g. your provider still uses NC 31, it prefers using a stable desktop client that works well with this version rather than the latest client version where the new features require a newer NC version (you donāt benefit from the new features, and you risk having new bugs).
But that is just a reasoning I came up with. If you want to debate the levels of certain messages, you have to check with the developers.
I fully understand, but this is with the stock client (thatās where the logic code is) and would happen against any version that is enterprise enabled, but NOT if you are community.
Just tested Nextcloud client version 33.0.2-1 (Debian built) and still the same
Itās a warning for a problem that doesnāt actually exist!
In this instance it really isnāt breaking anything, or will break anything, so it should be informational (or debug), and ONLY throw a warning if something is out of kilter. There is also no way to add a config entry to ignore it.
Sure - write a warning if something is wrong, but not if it is right!
Also note this doesnāt affect the server - just the client.
Odd to have to write a log script that says look for warnings and errors that I need to fix, but ignore THIS warning because it isnāt actually broken or going to break.
But the server (and the Nextcloud) you are using is an enterprise version.
That your Nextcloud admin does not ship their own desktop app is their decision, the protocol and everything with the community client is compatible, however there is a warning that the client is ācommunityā <=> āenterpriseā (server).
Also in terms of support, it comes back to your server admin. If they have a problem and it is an enterprise version, they have enterprise support (direct channel to Nextcloud, they donāt have to post here and hope to get help).
I have to code around it which means something isnāt right.
Quite simply it shouldnāt report this as a warning to the client (weāre not even talking about the server here) because nothing is broken. Thatās it.
Iāve opened and a bug, because it is in the client, and will leave it there.
