AppAPI default deploy daemon is not set

I’m having constant problems trying to use Nextcloud. It appears that one has to be a system administrator in order to use it at all, and I am not that. I have mail/web hosting on a shared server with my hosting company, and cannot run commands on the server myself. cPanel has Softaculous Apps Installer, and Softaculous had Nextcloud available to install, so I installed it. My hosting company is probably sick of my support requests now in trying to get Nextcloud to work.

Should I give up on Nextcloud? If so, is there a more user friendly alternative that doesn’t need constant system administrator fixes? I use it for files, CalendarDAV and ContactsDAV.

The current problem (below), cropped up and I don’t seem to have any way to deal with it other than make yet another support request to my hosting company.

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.0
  • Operating system and version (e.g., Ubuntu 24.04):
    • Linux, unknown type & version. Not given in cPanel.
  • Web server and version (e.g, Apache 2.4.25):
    • 2.4.65
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Unknown, can't find this in cPanel
  • PHP version (e.g, 8.3):
    • 8.3.23
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • Before Oct. 8 (logs go back that far)
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Softaculous
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • Unknown. Can't find this in cPanel.

Summary of the issue you are facing:

Nextcloud was working OK before, but now it says “AppAPI default deploy daemon is not set”. I searched how to set it, but it requires server access to Docker, which I do not have. I don’t even know if Docker is on this shared server. It must be, because Nextcloud 31.0.8 was installed, then updated to 31.0.9, then updated to 32.0.0. Updates all had problems that my hosting company had to fix. After the update to 32.0.0, Contacts & Calendar Apps were missing, so I installed again and luckily the DAV files were still there.

There are many errors I don’t know what to do with. “Slow session operation session_write_close detected” and “Tried to log in but could not verify token”. Also warnings I can’t do anything about because I don’t have server access.

From Log:

NotAuthenticated No public access to this resource., AppAPIAuth has not passed, This request is not for a federated calendar, No ‘Authorization: Basic’ header found. Either the client didn’t send one, or the server is misconfigured, No ‘Authorization: Bearer’ header found. Either the client didn’t send one, or the server is mis-configured, No ‘Authorization: Basic’ header found. Either the client didn’t send one, or the server is misconfigured
Uncaught exception

From Security & setup warnings:

AppAPI deploy daemon
AppAPI default deploy daemon is not set. Please register a default deploy daemon in the
settings to install External Apps (Ex-Apps).

Steps to replicate it (hint: details matter!):

  1. Unknown

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

{"reqId":"aOp56nOgUMdNSuG6ZFOwtQAAAA8","level":1,"time":"2025-10-11T15:38:18+00:00","remoteAddr":"23.111.78.182","user":"--","app":"no app in context","method":"GET","url":"/nextcloud/remote.php/dav","message":"Uncaught exception","userAgent":"Nextcloud Server Crawler","version":"32.0.0.13","exception":{"Exception":"Sabre\\DAV\\Exception\\NotAuthenticated","Message":"No public access to this resource., AppAPIAuth has not passed, This request is not for a federated calendar, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured","Code":0,"Trace":[{"file":"/home/windride/public_html/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.php","line":89,"function":"beforeMethod","class":"Sabre\\DAV\\Auth\\Plugin","type":"->","args":[{"__class__":"Sabre\\HTTP\\Request"},{"__class__":"Sabre\\HTTP\\Response"}]},{"file":"/home/windride/public_html/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php","line":456,"function":"emit","class":"Sabre\\DAV\\Server","type":"->","args":["beforeMethod:GET",[{"__class__":"Sabre\\HTTP\\Request"},{"__class__":"Sabre\\HTTP\\Response"}]]},{"file":"/home/windride/public_html/nextcloud/apps/dav/lib/Connector/Sabre/Server.php","line":211,"function":"invokeMethod","class":"Sabre\\DAV\\Server","type":"->","args":[{"__class__":"Sabre\\HTTP\\Request"},{"__class__":"Sabre\\HTTP\\Response"}]},{"file":"/home/windride/public_html/nextcloud/apps/dav/lib/Server.php","line":424,"function":"start","class":"OCA\\DAV\\Connector\\Sabre\\Server","type":"->","args":[]},{"file":"/home/windride/public_html/nextcloud/apps/dav/appinfo/v2/remote.php","line":22,"function":"exec","class":"OCA\\DAV\\Server","type":"->","args":[]},{"file":"/home/windride/public_html/nextcloud/remote.php","line":151,"args":["/home/windride/public_html/nextcloud/apps/dav/appinfo/v2/remote.php"],"function":"require_once"}],"File":"/home/windride/public_html/nextcloud/3rdparty/sabre/dav/lib/DAV/Auth/Plugin.php","Line":152,"message":"Uncaught exception","exception":[],"CustomMessage":"Uncaught exception"},"id":"68ea7ae78dd8e"}

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

N/A

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

No access

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => '<REDACTED>',
  'passwordsalt' => '<REDACTED>',
  'secret' => '<REDACTED>',
  'trusted_domains' => 
  array (
    0 => 'brucejohnson.ca',
  ),
  'datadirectory' => '<REDACTED>',
  'dbtype' => 'mysql',
  'version' => '32.0.0.13',
  'overwrite.cli.url' => 'https://brucejohnson.ca/nextcloud',
  'dbname' => '<REDACTED>',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => '<REDACTED>',
  'dbpassword' => '<REDACTED>',
  'installed' => true,
  'maintenance_window_start' => 1,
  'memcache.local' => '\\OC\\Memcache\\Memcached',
  'memcache.distributed' => '\\OC\\Memcache\\Memcached',
  'memcache.locking' => '\\OC\\Memcache\\Memcached',
  'mysql.utf8mb4' => true,
  'mail_smtpmode' => 'smtp',
  'mail_smtphost' => '<REDACTED>',
  'mail_sendmailmode' => 'smtp',
  'mail_smtpport' => '465',
  'mail_smtpsecure' => 'ssl',
  'mail_from_address' => '<REDACTED>',
  'mail_domain' => '<REDACTED>',
  'mail_smtpauth' => true,
  'mail_smtpname' => '<REDACTED>',
  'mail_smtppassword' => '<REDACTED>',
  'forbidden_filename_basenames' => 
  array (
    0 => 'con',
    1 => 'prn',
    2 => 'aux',
    3 => 'nul',
    4 => 'com0',
    5 => 'com1',
    6 => 'com2',
    7 => 'com3',
    8 => 'com4',
    9 => 'com5',
    10 => 'com6',
    11 => 'com7',
    12 => 'com8',
    13 => 'com9',
    14 => 'com¹',
    15 => 'com²',
    16 => 'com³',
    17 => 'lpt0',
    18 => 'lpt1',
    19 => 'lpt2',
    20 => 'lpt3',
    21 => 'lpt4',
    22 => 'lpt5',
    23 => 'lpt6',
    24 => 'lpt7',
    25 => 'lpt8',
    26 => 'lpt9',
    27 => 'lpt¹',
    28 => 'lpt²',
    29 => 'lpt³',
  ),
  'forbidden_filename_characters' => 
  array (
    0 => '<',
    1 => '>',
    2 => ':',
    3 => '"',
    4 => '|',
    5 => '?',
    6 => '*',
    7 => '\\',
    8 => '/',
  ),
  'forbidden_filename_extensions' => 
  array (
    0 => ' ',
    1 => '.',
    2 => '.filepart',
    3 => '.part',
  ),
  'loglevel' => 0,
  'maintenance' => false,
  'theme' => '',
);

Apps

The output of occ app:list (if possible).

No access

1 Like

It’s a server application, and it appears you’ve installed it yourself, so yes, you’re basically a system administrator at this point. :wink:

You can simply ignore that message or disable the app “AppAPI”.

I’m not 100 % sure whether that message is supposed to appear in the log, assuming you’re either on loglevel 2 or 3. If you are, and it does, it might be a bug.

Either way, since you can’t use it on a shared hosting platform anyway, just disable the app as mentioned above. The warning and related log entries should then disappear, or no longer appear, respectively.

2 Likes

Update. I’ve given up on Nextcloud and am using other tools to do what I want to do. My webhost thanked me when I told them.

2 Likes

Thanks Bruce. I just updated and was wondering if the whole mechanism had changed for future apps but was glad the solution was easy. Enabling apps without my input is a bit microsofty mind you.
Anyway, back to zero errors! thanks.

2 Likes

If you have found other tools that work better for you, that’s fine, and I’m glad to hear it. I mean that sincerely.

However, I’d like to clarify a few things here for other people who might read this:

  1. The message in the overview wasn’t an actual error, but rather the result of the AppAPI app being installed by default. Since no backend was configured, an error was shown on the setup page, which is expected behaviour. If you don’t plan to use it, simply disabling the app is an easy fix. Whether it should be enabled by default, is of course another discussion. (see my comment below)

  2. Having taken another look at the log message you posted, I noticed that it had a log level of 1. At this level, Nextcloud is extremely chatty, and it’s primarily intended to help developers and system administrators debug things. It should only be enabled temporarily if you experience any issues. As far as I know, the default log level is 2, so you wouldn’t have been bothered by those messages if the default hadn’t been changed. :wink:

3 Likes

You’re not wrong, and while I understand that they want more people to use the AppAPI, which obvioulsy will only happen if people are aware of its existence, I also knew it would lead to discussions on the forum from the moment I saw this “error” on my test server for the first time in one of the betas. :wink:

I am neither a developer nor a marketing professional, but I would argue that there must be more elegant ways to promote the AppAPI than enabling the app without asking and, as a result, greeting users with a red error message on the overview page after the upgrade. :wink:

2 Likes

I just upgraded to nextcloud 32 and got thios error in the administration page without any link on what Ex-Apps are, what is a deploy daemon, etc…

There is not even an indication it comes from an application.

There is also a big security risk having active application that I do not know about… So Why would I use this app ?

And it is not GitHub - nextcloud/app_api: Nextcloud AppAPI (I got there from the applications page) which can give me an information on its usage

However, it’s declared as an error, which I think is incorrect. That’s not the only situation NC issues an error that actually isn’t. I see potential to improve this.

I went to the “web site” of the GitHub - nextcloud/app_api: Nextcloud AppAPI App Api (its github page), and I do not understand what it is EXCEPT that looking at the doc, it seems to require docker ?

Is it true ?

Correct.

It’s an interface between NC and docker allowing to integrate applications running in a docker container. More complex applications might be provided as docker images rather than the way they have been provided in the past.

It is not explained anywhere !

And my system (FreeBSD) does not have docker

So the question is now : Should I begin to look for a nextcloud alternative ?

I know. NC has quite some lack in communication abilities. Even worse, I got the impression they know this quite well and don’t care. But it’s their product, so it’s their decision.

On the other hand: There is quite some information in the web, so it’s not much effort to find it.

Without knowing this, maybe there’s some proxy solution to allow to connect to an other host running docker.

As long as you don’t need apps that only come in a container: No.

1 Like

With the forced activation of AppAPI, it means the stock Nextcloud is now docker dependant.

I am not sure I want to handle the day when basic aplications like files or contacts depends on docker.

FIrst I will study and test the rollback procedures.

2 Likes

You could easily just deactive the related ApiApp.

1 Like

This is really frustrating. I just upgraded to version 32.0.1, and when I tried to find information on AppAPI via DuckDuckGo (my first stop when troubleshooting things) it gave me the NextCloud Docs page which just told me how to set things up. But no information that this was an App I could disable.

I came to the help forum to ask for help because information of what the error was and how to make it go away because I have no desire to us AI Slop or Docker Nonsense. I am very thankful for this thread, which made me aware that it was an app that was automagically enabled without so much as a How Do You Do to let me know they were trying to shove this nonsense down my throat.

I use NextCloud because usually it’s easy to work with, and they hadn’t previously pulled nonsense like this. I am not happy with them playing this game when it’s getting harder and harder to avoid enshittification everywhere on the web. >.<

3 Likes

That’s not true: https://docs.nextcloud.com/server/stable/admin_manual/exapps_management/AppAPIAndExternalApps.html

That depends on whether you actually need the additional features provided by AppAPI, and if there is an alternative at all that offers the same functionality as Nextcloud, with or without AppAPI, right?

Sure, you can probably provide WebDAV, CalDAV/CardDAV, and file synchronization with alternative solutions on FreeBSD, but even for those features, it’s not easy to find an “all-in-one” solution that integrates everything as seamlessly as Nextcloud does. And that’s not even considering all the additional features Nextcloud offers through regular apps.

And yes, for some time now, there’s been the AppAPI, which is currently used mainly by AI-related functionality integrated through the Nextcloud Assistant. If you don’t need any of that — which, again, are additional features — I don’t really see the issue. Just disable the app, the error message will go away, and your Nextcloud will continue to work exactly as before.

Sorry, talking about enshitification becuase of this is ridiculous. Nothing is being sold to you here, and you don’t have to use it, and yes, I also think that an “error message” is not the right way to promote additional features, but to talk about enshitification in relation to a product that delivers all features as FOSS is again ridiculous (I can’t think of a better word for it, sorry).

And yes, if you run relatively complex server software like Nextcloud, you have to look at the docs from time to time when updating, and if you had searched for AppAPI there, you would have found the explanation of what it is, and might then have come to the conclusion yourself that you could simply disable the app, or simply ignore the error message, which would also be an option, btw. :wink:

lol, okay. So enshittification isn’t the right word but you can’t come up with a better one?

NextCloud is not complicated. Until this point, I’ve found it pretty pain free to run on a cheap managed VPS. I’ve been using it for years now. Expecting clear communication from a project should not be asking too much. I did read the docs, and they were not clear about how one disables this “feature”, and telling me to ignore a warning message without understanding what it’s for? That’s straight up irresponsible.

Turning on a new feature primarily intended to enable AI, which is a very polarizing “technology” right now, is not a nothing choice. To do it without making it clear to admins how to turn it off if they don’t want it is on the enshittification side of the fence.

Please don’t condescend me.

That refers to ridiculous, which I used twice in the same paragraph.

Nextcloud is relatively complex, and no, just because you, for once, didn’t understand something right away or had to look it up, it doesn’t make it any more or less complex, and the fix in this case is literally one click on the “disable” button of the app.

Well then, call it enshitification, if you need to. For me, it would be enshitification if you were forced to use it or if it were an “upselling” feature. If parts of the software were proprietary and only available for a fee. But of course, there are also people who make a huge fuss when, for example, a developer of a popular Gnome extension dares to integrate a donate button into their software, which can be removed with a single click. And that’s where I would use the word ridiculous again. :wink:

Here’s a summary of how I see it.

  1. From a purely technical point of view, the error message is correct, because the AppAPI doesn’t work without the backend, so it’s correct to alert the user to this, and yes, it is technically an error if the backend is missing.

  2. Should the app have been enabled by default? I don’t think so.

  3. Does that justify calling the whole thing “enshitfication” and putting it on a par with “robber baron” companies like Broadcom, Oracle, Microsoft, etc.? In my humble opinion, no.

So that’s all from me, and now have a nice day, everyone, and happy Nextclouding, or maybe not, if you decide to leave Nextcloud because of this. :wink:

1 Like