# yunohost app upgrade
Warning: 2017-12-19 15:12:50 URL:https://github-production-release-asset-2e65be.s3.amazonaws.com/3564353/c2cba910-65ec-11e6-927d-35c912bee0d9?X-Amz-
Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20171219%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171219T141247Z&X-Amz-Expires=
300&X-Amz-Signature=b1454c6acc4812297eeaf061c63a73c34ddf171dba2ef6b4d8b4c9efb147a5c2&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=
attachment%3B%20filename%3Dbaikal-0.4.6.zip&response-content-type=application%2Foctet-stream [3288478/3288478] -> "app.zip" [1]
Warning: Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.
Warning: !!
Warning: baikal's script has encountered an error. Its execution was cancelled.
Warning: !!
Warning: Upgrade failed.
Warning: 'yunohost app checkurl' is deprecated and will be removed in the future
Warning: The app was restored to the way it was before the failed upgrade.
Error: Unable to upgrade baikal
Error: No app to upgrade
exception 'Exception' with message 'Specific/config.php is not writable. Please give write permissions to httpd user on file 'Specific/config.php'.' in /var/www/baikal/Core/Frameworks/Baikal/Core/Tools.php:87
Stack trace:
#0 /var/www/baikal/Core/Frameworks/Baikal/Framework.php(80): Baikal\Core\Tools::assertBaikalIsOk()
#1 /var/www/baikal/html/index.php(52): Baikal\Framework::bootstrap()
#2 {main}
# tail /var/log/nginx/error.log
2017/12/19 14:49:40 [notice] 5102#0: signal process started
2017/12/19 14:54:27 [info] 620#0: Using 32768KiB of shared memory for push module in /etc/nginx/nginx.conf:63
2017/12/19 14:54:27 [info] 620#0: [lua] init.lua:57: SSOwat ready
2017/12/19 15:12:56 [emerg] 2668#0: duplicate location "/.well-known/caldav" in /etc/nginx/conf.d/myServer.org.d/nextcloud.conf:4
2017/12/19 15:13:05 [notice] 2723#0: signal process started
2017/12/19 15:14:44 [notice] 2797#0: signal process started
2017/12/19 15:23:51 [emerg] 3373#0: duplicate location "/.well-known/caldav" in /etc/nginx/conf.d/myServer.org.d/nextcloud.conf:4
2017/12/19 15:24:01 [notice] 3432#0: signal process started
2017/12/19 15:25:40 [notice] 3511#0: signal process started
2017/12/19 16:05:32 [notice] 4796#0: signal process started
Do you think that the fact that both nextcloud and baikal are trying to use “/.well-known/caldav” does explain why the baikal upgrade has failed (my 1st message yesterday)?
Yes, sorry I was not clear.
Your baikal install failed because of that:
Warning: Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.
And your nginx log says
2017/12/19 15:23:51 [emerg] 3373#0: duplicate location "/.well-known/caldav" in /etc/nginx/conf.d/myServer.org.d/nextcloud.conf:4
So, I think that the reason why baikal failed to install. And also, why we didn’t see that before, we never try an app with another already installed. And I suppose nobody had this error during the testing.
You mean that nobody in the testers’ group has nextcloud + baikal previously installed, before upgrading baikal?
For you to know, on my side, I had baikal installed before I installed owncloud. Then I upgraded owncloud to nextcloud. Then I tried to upgrade baikal…
I’m not even sure anyone have tried the testing branch of baikal…
As I said, I don’t know much about this part of baikal and nextcloud.
But, as I can read in the script, I think you can try to comment your entries about ‘.well-known’ in your nextcloud setup and retry to upgrade baikal.