Nextcloud app api path

In my config.php my path to nextcloud app store is:

‘appstoreurl’ => ‘’,

but if am checking the logfile I get error messages like that:

Error core Could not get application: cURL error 7: Failed to connect to port 443: Connection timed out

Is it my problem or a problem with the web?

That’s because the URL is wrong. Use ‘appstoreurl’ => ‘’,

Maybe it will be good to change it in the docu as well.
Thanks, now it is working

Which docs, can you post a link?

Docs I’m using are from

It is in the official docu of nextcloud in howto config it.

There is the link for the appstore

Section is here:

Can you create a pull request on github?

I have checked the link but didn’t found the path to the api store.

Now I have changed it in my config file and the link seems to be ok but am getting now an error if I try to update apps.
That is I do not understand cause it was working a while before.
The error is : Directory name must not be empty.
What does it means?

No idea, paste your config

Also clear your opcode cache, as in: restart your web server

I restarted my browser and cleared my cache.
Here is my config:

<?php $CONFIG = array ( 'instanceid' => '', 'passwordsalt' => '', 'secret' => '', 'trusted_domains' => array ( 0 => '', 1 => '', 2 => '', ), 'datadirectory' => '/media/cloud/nextcloud/data', 'overwrite.cli.url' => '', 'dbtype' => 'mysql', 'version' => '', 'dbname' => 'owncloud', 'dbhost' => 'localhost', 'dbtableprefix' => 'oc_', 'dbuser' => '', 'dbpassword' => '', 'logtimezone' => 'UTC', 'installed' => true, 'forcessl' => true, 'default_language' => 'de', 'defaultapp' => 'files', 'knowledgebaseenabled' => true, 'allow_user_to_change_display_name' => true, 'remember_login_cookie_lifetime' => 1296000, 'session_lifetime' => 86400, 'session_keepalive' => true, 'mail_smtpmode' => 'smtp', 'mail_smtphost' => '', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => true, 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => '', 'mail_smtppassword' => '', 'mail_from_address' => 'owncloud', 'has_internet_connection' => true, 'appstoreenabled' => true, 'appstoreurl' => '', 'apps_paths' => array ( 0 => array ( 'path' => '/var/www/nextcloud/apps', 'url' => '/apps', 'writable' => true, ), ), 'appcodechecker' => true, 'updatechecker' => true, 'updater.server.url' => '', 'check_for_working_webdav' => true, 'check_for_working_wellknown_setup' => true, 'loglevel' => 2, 'theme' => '', 'maintenance' => false, 'mail_smtpport' => '587', 'overwritewebroot' => '/nextcloud', 0 => true, 'enable_avatars' => true, 'memcache.local' => '\\OC\\Memcache\\Redis', 'debug' => true, 'trashbin_retention_obligation' => 'auto', 'filelocking.enabled' => 'true', 'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array ( 'host' => 'localhost', 'port' => 6379, 'timeout' => 0.0, 'dbindex' => 0, ), 'appstore.experimental.enabled' => true, 'htaccess.RewriteBase' => '/nextcloud', );

Problem with update APPS still exist.
If I try to update or activate a app I get a error message on the admin page.
The error is:

Directory name must not be empty.

No idea, probably unrelated to the new API since it works just fine for everyone else.

If I deactivate - delete - transfer - and activate the new app all is working fine.
That means the app is ok. It only accurs if I want to update the app via the function on the admin

So for the old app store the app identifier was the OCS ID (a number like 185023). That means that if you’ve installed the same app but the ID is different, it won’t be recognized as the same app. The same is true for updates.

The new app store mimics this behavior for the Nextcloud 10/9 API: only apps that provide an OCS ID will be available for 9 and 10 however it’s not an absolute must that the OCS IDs must match the ones from the ownCloud app store. It’s of course highly recommended.

My guess is that whatever app you are trying to update is either not available in the new app store or the OCS ID does not match

PS: the same issue is also present if you use the old app store. It’s an API deficiency if you ask me and nothing that can be fixed. Nextcloud 11 however will use the new API which does not have this issue anymore