Git Product home page Git Product logo

cryptpad_ynh's Introduction

CryptPad for YunoHost

Integration level Working status Maintenance status

Install CryptPad with YunoHost

Read this README in other languages.

This package allows you to install CryptPad quickly and simply on a YunoHost server.
If you don't have YunoHost, please consult the guide to learn how to install it.

Overview

CryptPad is a collaboration suite that is end-to-end-encrypted and open-source. It is built to enable collaboration, synchronizing changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.

Shipped version: 5.3.0~ynh2

Demo: https://cryptpad.fr/

Screenshots

Screenshot of CryptPad

Documentation and resources

Developer info

Please send your pull request to the testing branch.

To try the testing branch, please proceed like that:

sudo yunohost app install https://github.com/YunoHost-Apps/cryptpad_ynh/tree/testing --debug
or
sudo yunohost app upgrade cryptpad -u https://github.com/YunoHost-Apps/cryptpad_ynh/tree/testing --debug

More info regarding app packaging: https://yunohost.org/packaging_apps

cryptpad_ynh's People

Contributors

alexaubin avatar ddataa avatar ericgaspar avatar frju365 avatar genma avatar jimbojoe avatar magikcypress avatar rodinux avatar roipoussiere avatar rungeard avatar saimyx avatar shinenelson avatar tagadda avatar tituspijean avatar yalh76 avatar yunohost-bot avatar zeroheure avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar

Forkers

dfjerstad nemsia rafi594 genma roipoussiere njoyard amyblais shinenelson manuelleduc jrd10 yashodhank rungeard zcadqewxs wayneoutthere zeroheure rodinux ddataa smalldanmom lab-8916100448256

cryptpad_ynh's Issues

Upgrade loses admin key from config.js

Describe the bug

When running any upgrade to CryptPad on Yunohost, the admin key is lost from config.js

Context

  • Hardware: Raspberry Pi 4
  • YunoHost version: 11.1.15
  • I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • If upgrading, current package version: 5.2.1~ynh6

Steps to reproduce

  • Click "System Update" in Yunohost admin screen
  • Request pending upgrade to CryptPad
  • On completion config.js has been replaced with a vanilla version with no admin key so no administration is possible without manual edits of config.js

Expected behavior

Install should preserve admin key and perhaps some other changes to config.js that are necessary for normal operation

Logs

https://paste.yunohost.org/raw/atukamafes

Update from v4 never worked, including 5.2.1~ynh8

Hi!

Yunohost 11.1.18
Update from Cryptpad 4.12.0~ynh2 to 5.2.1~ynh6 had an CORS issue with the sandbox domain, as the target url was in 404 error
Update from 5.2.1~ynh6 to 5.2.1~ynh8 has another issue: Cryptad logo stay still, as "the ressource has been blocked because of an incorrect MIME type" and obviously, the Cryptad service is down, see the log below.

-- Journal begins at Wed 2022-10-26 10:26:11 CEST, ends at Mon 2023-04-17 20:41:18 CEST. --
avril 17 20:41:11 systemd[1]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
avril 17 20:41:11 systemd[1]: Started CryptPad: Zero Knowledge realtime collaborative editor..
avril 17 20:41:12 npm[2836583]: npm does not support Node.js v8.17.0
avril 17 20:41:12 npm[2836583]: You should probably upgrade to a newer version of node as we
avril 17 20:41:12 npm[2836583]: can't make any promises that npm will work with this version.
avril 17 20:41:12 npm[2836583]: You can find the latest version at https://nodejs.org/
avril 17 20:41:12 npm[2836583]: /opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/npm.js:32
avril 17 20:41:12 npm[2836583]:   #unloaded = false
avril 17 20:41:12 npm[2836583]:   ^
avril 17 20:41:12 npm[2836583]: SyntaxError: Invalid or unexpected token
avril 17 20:41:12 npm[2836583]:     at createScript (vm.js:80:10)
avril 17 20:41:12 npm[2836583]:     at Object.runInThisContext (vm.js:139:10)
avril 17 20:41:12 npm[2836583]:     at Module._compile (module.js:617:28)
avril 17 20:41:12 npm[2836583]:     at Object.Module._extensions..js (module.js:664:10)
avril 17 20:41:12 npm[2836583]:     at Module.load (module.js:566:32)
avril 17 20:41:12 npm[2836583]:     at tryModuleLoad (module.js:506:12)
avril 17 20:41:12 npm[2836583]:     at Function.Module._load (module.js:498:3)
avril 17 20:41:12 npm[2836583]:     at Module.require (module.js:597:17)
avril 17 20:41:12 npm[2836583]:     at require (internal/module.js:11:18)
avril 17 20:41:12 npm[2836583]:     at module.exports (/opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/cli.js:22:15)
avril 17 20:41:12 systemd[1]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
avril 17 20:41:12 systemd[1]: cryptpad.service: Failed with result 'exit-code'.
avril 17 20:41:12 systemd[1]: cryptpad.service: Scheduled restart job, restart counter is at 4.
avril 17 20:41:12 systemd[1]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
avril 17 20:41:12 systemd[1]: Started CryptPad: Zero Knowledge realtime collaborative editor..
avril 17 20:41:12 npm[2836591]: npm does not support Node.js v8.17.0
avril 17 20:41:12 npm[2836591]: You should probably upgrade to a newer version of node as we
avril 17 20:41:12 npm[2836591]: can't make any promises that npm will work with this version.
avril 17 20:41:12 npm[2836591]: You can find the latest version at https://nodejs.org/
avril 17 20:41:12 npm[2836591]: /opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/npm.js:32
avril 17 20:41:12 npm[2836591]:   #unloaded = false
avril 17 20:41:12 npm[2836591]:   ^
avril 17 20:41:12 npm[2836591]: SyntaxError: Invalid or unexpected token
avril 17 20:41:12 npm[2836591]:     at createScript (vm.js:80:10)
avril 17 20:41:12 npm[2836591]:     at Object.runInThisContext (vm.js:139:10)
avril 17 20:41:12 npm[2836591]:     at Module._compile (module.js:617:28)
avril 17 20:41:12 npm[2836591]:     at Object.Module._extensions..js (module.js:664:10)
avril 17 20:41:12 npm[2836591]:     at Module.load (module.js:566:32)
avril 17 20:41:12 npm[2836591]:     at tryModuleLoad (module.js:506:12)
avril 17 20:41:12 npm[2836591]:     at Function.Module._load (module.js:498:3)
avril 17 20:41:12 npm[2836591]:     at Module.require (module.js:597:17)
avril 17 20:41:12 npm[2836591]:     at require (internal/module.js:11:18)
avril 17 20:41:12 npm[2836591]:     at module.exports (/opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/cli.js:22:15)
avril 17 20:41:12 systemd[1]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
avril 17 20:41:12 systemd[1]: cryptpad.service: Failed with result 'exit-code'.
avril 17 20:41:12 systemd[1]: cryptpad.service: Scheduled restart job, restart counter is at 5.
avril 17 20:41:12 systemd[1]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
avril 17 20:41:12 systemd[1]: cryptpad.service: Start request repeated too quickly.
avril 17 20:41:12 systemd[1]: cryptpad.service: Failed with result 'exit-code'.
avril 17 20:41:12 systemd[1]: Failed to start CryptPad: Zero Knowledge realtime collaborative editor..

seems to be a Node.js error? Thanks !

Error accesing Cryptpad

I just installed Cryptpad to my yunohost server. I already have a domain, and I have added a new one because it says Cryptpad needs its own domain.

After adding the new domain, I install the app and no errors are shown, but when I try to access the page remains blank. In the browser console I see errors loading some resources:

Any guess?

Error 500:
https://mynewdomain/bower_components/requirejs/require.js?ver=2.3.5
https://mynewdomaincustomize/main-favicon.png

Error 404:
https://mynewdomain/ynhpanel.js

[Installation] Error Nodejs version

Hello,

During my installation I have got problem. In fact, I got this error:

-- Installing helper scripts in '/opt/node_n/bin'...
=== n successfully installed.
  Run `n stable` to install the latest stable Node.js version.

  Run `n -h` for help.
  To update n later, run `n-update`.
  To uninstall, run `n-uninstall`.

  IMPORTANT: OPEN A NEW TERMINAL TAB/WINDOW or run `. /root/.bashrc`
             before using n and Node.js.
===
+ PATH=/opt/node_n/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ test -x /usr/bin/node_n
+ test -x /usr/bin/npm_n
+ n 8

     install : node-v8.6.0

  Error: invalid version 8.6.0

How can I solve this issue?

Thank you very much

Checkup tests failing

Describe the bug

The installationdomain.tld/checkup page complains about several things.

Context

  • Hardware: any
  • YunoHost version: any (currently v4.2.6.1)
  • I have access to my server: any means
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: v4.8.0 and earlier

Steps to reproduce

Install the app and reach the checkup page.

Expected behavior

No or minimal complaints.

Logs

Let's make it a to-do list. Some tasks might be deemed unnecessary.

  • httpUnsafeOrigin and httpSafeOrigin are equivalent. In order for CryptPad's security features to be as effective as intended they must be different. See cryptpad/config/config.js
  • This instance's encrypted support ticket functionality has not been enabled. This can make it difficult for its users to safely report issues that concern sensitive information. This can be configured via the admin panel's Support tab.
  • This instance has not been configured to support web administration. This can be enabled by adding a registered user's public signing key to the adminKeys array in cryptpad/config/config.js. (this one has to be done manually IIRC)
  • Missing HTTP headers required for .xlsx export from sheets. A value of require-corp was expected for the cross-origin-embedder-policy HTTP header, but instead a value of "" was received.
  • /api/config was served with duplicated or incorrect headers. Compare your reverse-proxy configuration against the provided example.
  • The cross-origin-resource-policy header for /api/config is '' instead of 'cross-origin' as expected.
  • The cross-origin-embedder-policy header for /api/config is '' instead of 'require-corp' as expected.
  • Same as the three /api/config above, with /api/broadcast instead
  • /some/page does not have the required 'content-security-policy' headers set

Problème Installation.

Bonjour,
L'app ne fonctionne pas. Problème dans les dépendances + Type error. Une issue a été ouverte : cryptpad/cryptpad#147.
Elle devrait être fixé avant la fin de la semaine, je l'espère.
frju365

Validate quality level 4 conformance (SSO integration)

SSO can't be enabled due to a Cryptpad known limitation:

CryptPad's login strategy is to use your username and password to derive a secret which is used to access and encrypt/decrypt the realtime object which contains all of the information you see in your drive.
So until an enhancement of cryptad,

Confirmed by this discussion with a cryptpad developer:

JimboJoe - Hi, I'm sorry if that question has already been asked, I couldntt find a definitive written answer: Do you confirm you can't actually change your password or use any other authentication method (like LDAP)?
aaron macsween - hi JimboJoe, currently there's no means of changing your password, as it's used to derive the encryption keys for your drive

Validate quality level 5 conformance

This level needs to be formally assessed as there are residual warnings stated by package_linter

Level 5 is forced on this package due to one false positive:

>>>> INSTALL SCRIPT <<<<
✔ Only helpers are used
✔ no 'exit' command found: 'ynh_die' helper is possibly used
✔ Verifications (with 'ynh_die' or 'exit' commands) are done before any system modification.
✘ set -eu is missing at beginning of file. For details, look at https://dev.yunohost.org/issues/419
✔ Argument retrieval from manifest seems to be done with environement variables

Due to this bug in package linter (Don't check "set -eu" in install script if it uses ynh_abort_if_errors).

Upgrade from 4.12.0~ynh2 to 5.2.1~ynh4 involve loss of data - empty spreedsheats

Hello,

We made the upgrade from 4.12 version to 5.2.1 version of cryptpad and some (all ?) users complained because when they tried to open their documents it proposed to them to update this document and the document ends empty.

I will try to restore an 4.12 versio on another server, but just to say be careful in case you do this update to have ways to roll it back in case it goes wrong

just white page

Just installed the news version of cryptpad - installation went find - gree light...
but when i go to the domain I just get a wite page...

if I look up the scours code it will show:

<!DOCTYPE html>
<html class="cp" id="four-oh-four">
<!-- If this file is not called customize.dist/src/template.html, it is generated -->
<head>
    <title data-localization="main_title">CryptPad: Zero Knowledge, Collaborative Real Time Editing</title>
    <meta content="text/html; charset=utf-8" http-equiv="content-type"/>
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
    <link rel="icon" type="image/png" href="/customize/main-favicon.png" id="favicon"/>
    <script async data-bootload="/customize/four-oh-four.js" data-main="/common/boot.js?ver=1.0" src="/bower_components/requirejs/require.js?ver=2.3.5"></script>
<script type="text/javascript" src="/ynh_portal.js"></script><link type="text/css" rel="stylesheet" href="/ynh_overlay.css"></link><script type="text/javascript" src="/ynhtheme/custom_portal.js"></script><link type="text/css" rel="stylesheet" href="/ynhtheme/custom_overlay.css"></link></head>
<body class="html">
<noscript>
<h1>404</h1>
<h3>We couldn't find the page you were looking for</h3>

</noscript>

Customize Look and Feel

Once installed, this app looks like the original https://www.cryptpad.fr website, which is very confusing.

But it provides a supported way to customize the look and feel which is detailed here, and that could be used to get a neutral YunoHost look and feel.

Where would be the best design/graphics materials to begin from? Are there any volunteer web designers?

CryptPad community

Hello folks,

I'm very sorry I erased the issue template.

Just wanted to be sure you had the information we opened our community forum recently and if you happen to need any help regarding packaging CryptPad for YunoHost you can ask over here. We also have a dedicated "Distribution" tag for community maintained projects. 😊

Don't hesitate to join us!

Can't keep avatars for profile or groups

Describe the bug

Since the upgrade to 5.2.1, the images for avatars in profiles our for groups seems broken links

Context

  • Hardware: VPS bought online
  • YunoHost version: 11.1.6.2
  • I have access to my server: *Through SSH | through the webadmin *
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
    • If yes, please explain:
  • Using, or trying to install package version/branch: master
  • If upgrading, current package version: 5.2.1

Steps to reproduce

  1. *Since connected (with admin account), the aavatr is a broken link in the menu.
  2. Go to 'Profil', the avatar is still a broken link
  3. Remove the avatar and replace and download a new one. (same occurs in administration Groups)*
  4. All seems OK, disconnect the session
  5. Connect again, for a new session
  6. The images are broken links again

Expected behavior

I would keep the images download for avatars or for groups stay in place and don't see broken links each time I connect for a new session

Logs

I can see this in the console message

Blocage d’une requête multiorigine (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://cryptpad.linux07.fr/blob/41/4121b7811c5d4f645b1a0ce02980a1e35c35be00b2e96f4c. Raison : l’en-tête CORS « Access-Control-Allow-Origin » ne correspond pas à « 'https://sandbox-cryptpad.linux07.fr/' ».

In the inspect console

Capture d’écran du 2023-02-19 13-30-59

Also

XHR_ERROR 2 [common-mediatag.js:86:21](https://cryptpad.linux07.fr/common/inner/common-mediatag.js?ver=5.2.1-1676807666302)
    displayMediatagImage https://cryptpad.linux07.fr/common/inner/common-mediatag.js?ver=5.2.1-1676807666302:86
    emit https://cryptpad.linux07.fr/common/media-tag.js?ver=5.2.1-1676807666302:651
    emit https://cryptpad.linux07.fr/common/media-tag.js?ver=5.2.1-1676807666302:648
    error https://cryptpad.linux07.fr/common/media-tag.js?ver=5.2.1-1676807666302:693
    dl https://cryptpad.linux07.fr/common/media-tag.js?ver=5.2.1-1676807666302:742

Or

<span class="message-body-wrapper"><span class="message-flex-body"><span class="message-body devtools-monospace"><span class="method">GET</span><span class="url" title="https://sandbox-cryptpad.linux07.fr/images/broken.png">https://sandbox-cryptpad.linux07.fr/images/broken.png</span><a class="status"><span class="status-info">[HTTP/2 <span class="status-code" data-code="404" title="En savoir plus">404</span> Not Found 46ms]</span></a></span> </span><div class="network-info network-monitor"><div class="devtools-sidebar-tabs"><div class="tabs "><nav class="tabs-navigation"><ul class="tabs-menu" role="tablist"><li class="tabs-menu-item panel-with-code is-active" role="presentation"><span class="devtools-tab-line"></span></li></ul></nav></div></div></div></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><span class="devtools-tab-line"></span></span><span class="message-body-wrapper"><div id="headers-panel" style="visibility: visible; height: 100%;" class="tab-panel-box" role="tabpanel" aria-labelledby="headers-tab"><div class="tab-panel panel-with-code"><div class="headers-panel-container"><div class="devtools-toolbar devtools-input-toolbar"><div class="devtools-searchbox"><input class="devtools-filterinput" placeholder="Filtrer les en-têtes" type="search" value=""></div></div><div class="panel-container"><div class="headers-overview"><div class="url-preview"><div class="properties-view"><div class="tree-container">

  |  
-- | --
GET | https://sandbox-cryptpad.linux07.fr/images/broken.png

</span>GEThttps://sandbox-cryptpad.linux07.fr/images/broken.png
[HTTP/2 404 Not Found 46ms]

	
GET
	https://sandbox-cryptpad.linux07.fr/images/broken.png
État
404
Not Found
VersionHTTP/2
Transfert1,99 Ko (taille 801 o)
Politique de référentstrict-origin-when-cross-origin
Priorité de la requêteHigh

	
access-control-allow-origin
	'https://sandbox-cryptpad.linux07.fr/'
cache-control
	no-cache
content-length
	801
content-security-policy
	default-src 'none'; child-src https://cryptpad.linux07.fr/; worker-src 'self'; media-src blob:; style-src 'unsafe-inline' 'self' https://cryptpad.linux07.fr/; script-src 'self' resource: https://cryptpad.linux07.fr/; connect-src 'self' blob: https://cryptpad.linux07.fr/ https://sandbox-cryptpad.linux07.fr/ wss://cryptpad.linux07.fr; font-src 'self' data: https://cryptpad.linux07.fr/; img-src 'self' data: blob: https://cryptpad.linux07.fr/; frame-src 'self' https://sandbox-cryptpad.linux07.fr/ blob:; frame-ancestors 'self' https://cryptpad.linux07.fr/
content-type
	text/html
cross-origin-embedder-policy
	require-corp
cross-origin-resource-policy
	cross-origin
date
	Sun, 19 Feb 2023 12:36:02 GMT
etag
	"63a31969-321"
permissions-policy
	interest-cohort=()
server
	nginx
strict-transport-security
	'max-age=31536000; includeSubDomains' always
x-content-type-options
	nosniff
x-download-options
	noopen
X-Firefox-Spdy
	h2
x-frame-options
	SAMEORIGIN
x-permitted-cross-domain-policies
	none
x-sso-wat
	You've just been SSOed
x-xss-protection
	'1; mode=block'
	
Accept
	image/avif,image/webp,*/*
Accept-Encoding
	gzip, deflate, br
Accept-Language
	fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
Cache-Control
	max-age=0
Connection
	keep-alive
DNT
	1
Host
	sandbox-cryptpad.linux07.fr
Referer
	https://sandbox-cryptpad.linux07.fr/profile/inner.html?ver=5.2.1-1676807666302
Sec-Fetch-Dest
	image
Sec-Fetch-Mode
	no-cors
Sec-Fetch-Site
	same-origin
Sec-GPC
	1
TE
	trailers
User-Agent
	Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0

Cannot access the admin area

I am sorry for not following the template, but the issue is this: I run the latest YunoHost + latest Cryptpad. I installed it correctly. All fine. I made an account. Then edited var/www/cryptpad/config/config.js. and added my account's public key. Restarted cryptpad. Tried to access /admin and I get "Only administrators can access this page". Also rebooted the server just in case. Am I doing something wrong? Thanks!

Files/Folders with 0777 file permission 

/var/www/cryptpad/node_modules/.bin/lesshint
/var/www/cryptpad/node_modules/.bin/shjs
/var/www/cryptpad/node_modules/.bin/errno
/var/www/cryptpad/node_modules/.bin/get-folder-size
/var/www/cryptpad/node_modules/.bin/image-size
/var/www/cryptpad/node_modules/.bin/uuid
/var/www/cryptpad/node_modules/.bin/sshpk-conv
/var/www/cryptpad/node_modules/.bin/js-yaml
/var/www/cryptpad/node_modules/.bin/sshpk-verify
/var/www/cryptpad/node_modules/.bin/jshint
/var/www/cryptpad/node_modules/.bin/cssesc
/var/www/cryptpad/node_modules/.bin/mkdirp
/var/www/cryptpad/node_modules/.bin/mime
/var/www/cryptpad/node_modules/.bin/rimraf
/var/www/cryptpad/node_modules/.bin/strip-json-comments
/var/www/cryptpad/node_modules/.bin/sshpk-sign
/var/www/cryptpad/node_modules/.bin/atob
/var/www/cryptpad/node_modules/.bin/esparse
/var/www/cryptpad/node_modules/.bin/esvalidate
/var/www/cryptpad/node_modules/.bin/lessc

I am not sure if these need to be changed. Let me know.

Add security hardening

It is strongly recommended to set in www/common/application_config_internal.js a randomly chosen string as a salt for the password hashing. This makes it such attackers who want to bruteforce common credentials must do so again on each CryptPad instance that they wish to attack.

Context

  • Hardware: VPS bought online / Old laptop or computer / Raspberry Pi at home / Internet Cube with VPN / Other ARM board / ...
  • YunoHost version: 11.1.15
  • I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen | ...
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: stable
  • If upgrading, current package version: 5.2.1~ynh8

Steps to reproduce

After the installation if I create the first user on the application, I can't do this security operation or it will break the authentication.

The loginSalt should only be set when your CryptPad instance is first created. Changing it at a later time will break logins for all existing users.

For this, we need insert a chosen string in the following line:

AppConfig.loginSalt = '';

We may further want to increase the minimum password length. For this, modify the following line:

AppConfig.minimumPasswordLength = 8;

Expected behavior

Have script to do this with a ramdom key to include in this file, perhaphs something like this ??

secret_key=$(ynh_string_random --length=30)`
ynh_replace_string --match_string="AppConfig.loginSalt = '';" --replace_string="AppConfig.loginSalt ='$key';" --target_file="$install_dir/www/common/application_config_internal.js"
ynh_replace_string --match_string="AppConfig.minimumPasswordLength = 8;" --replace_string="AppConfig.minimumPasswordLength = 20;" --target_file="$install_dir/www/common/application_config_internal.js"

This means the key must be saved with an upgrade, I am not sure if it is possible to have this on upgrade script ??

It is only suggestions...

Perhaps it is most easier have a template and do ynh_add_config --template="../conf/application_config_internal.js" --destination="$install_dir/config/application_config_internal.js"

Failed upgrade to 1.27.0

Hello,

I tried the upgrade to 1.22 version, but it failed when trying to update dependencies.
I am currently at 1.20 (I think)... indeed the info about the apps shows 1.15.0 but it seems the downloaded version is 1.20 and the upgrade should be 1.22.
Maybe the diversity of version between the manifest.json, the app.src and de readme is creating confusion during the upgrade precess.
I can send you some more info of the failed upgrade if you need.

Crou²

Yunohost floating logo thingy doesn't take me back to SSO

Describe the bug

After installing Cryptpad in Yunohost, clicking the Cryptpad tile, and launching the app, I am unable to return to the Yunohost single sign on (SSO) by clicking the floating Yunohost logo thingy.

Clicking should take me to: https://pad.domain.com/yunohost/sso/

Instead I get this in firefox: Blocked Page: An error occurred during a connection to pad.domain.com

This in Chrome: pad.domain.com refused to connect.

Context

  • Hardware: *Digital ocean debian droplet
  • YunoHost version: 11.0.10.2 (stable)
  • I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen | ...
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no. Unless installing on a subdomain is 'special'. It's on a subdomain 'pad.domain.com'
  • Using, or trying to install package version/branch: using 4.12.0~ynh2

Steps to reproduce

Log in as user.
Click Cryptpad tile
Click YH floating logo
see error messages described above manifest...

Expected behavior

Clicking YH floating logo takes you to https://pad.domain.com/yunohost/sso/

Logs

  • None

From standard stable install : checkup failed with 19 / 25 tests passed

Describe the bug

In a fresh standard yunohost VPS server, install cryptpad app.
A warning during install mention that instance is not secure and not ready for production since checkup has not passed succesfully.
Go on page https://mycryptpaddomain.com/checkup

result is 19 / 25 tests passed

failed test 4
It appears that you are trying to load this page via an origin other than its main domain (https://myyunohostmaindomain.com). See the httpUnsafeOrigin option in cryptpad/config/config.js which is exposed via /api/config.

failed test 15
support ticket functionnality not enabled

failed test 16
web admin not setup

failed test 5
The main domain (configured via httpUnsafeOrigin as https://mycryptpaddomain.com in cryptpad/config/config.js and exposed via /api/config) could not be reached.

failed test 18
/common/onlyoffice/v4/web-apps/apps/spreadsheeteditor/main/index.html does not have the required 'content-security-policy' headers set. This is most often related to incorrectly configured sandbox domains or reverse proxies.

failed test 17
/sheet/inner.html does not have the required 'content-security-policy' headers set. This is most often related to incorrectly configured sandbox domains or reverse proxies.

Context

  • Hardware: VPS
  • YunoHost version: 4.3.6.3
  • I have access to my server: ssh & web adm
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: latest stable
  • current package version: 4.12.0~ynh2

Steps to reproduce

Deploy cryptpad application and go on checkup page

Expected behavior

All checks shall be valid and if some necessary configuration as to be made by admin (test 15 & 16) notify clearly admin about it

Where is config.js ?

Hello,

I just install the app and i'd like to configure it, but the file mentioned in the readme doesn't exist, there's no config.js in /var/www/cryptpad. How am i supposed to configure my instance ?

blank windows after login next an upgrade

Describe the bug

after upgrade, I could login, but clicking on the avatar and menu, a blank (black) window appears

Context

  • Hardware: *Public cloud *
  • YunoHost version: 4.3.3
  • I have access to my server: *Through SSH | through the webadmin *
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
  • If yes, please explain: I have moved the partition /var/www/cryptpad on an external disk
  • Using, or trying to install package version/branch: 4.12.1 master

Steps to reproduce

  • If you performed a command from the CLI, the command itself is enough. For example: 
    sudo yunohost tools upgrade --apps

Log in after successful upgrade is ok, but I can't see my drive, whenI clic on the avatar with the menu, only a blank page, black because of my theme, appears and nothing more...

Expected behavior

*after login, I need found my drive and contacts, etc... *

Logs

this was the log upgrade

description: Upgrade the 'cryptpad' app
log_path: /var/log/yunohost/categories/operation/20211126-213527-app_upgrade-cryptpad.log
logs: 
  - 2021-11-26 21:41:17,400: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,400: INFO - The service cryptpad has correctly executed the action start.
  - 2021-11-26 21:41:17,411: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,424: DEBUG - + ynh_script_progression '--message=Reloading NGINX web server...' --weight=1
  - 2021-11-26 21:41:17,424: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,499: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,513: DEBUG - + echo '! Helper used in legacy mode !'
  - 2021-11-26 21:41:17,513: DEBUG - + set +x
  - 2021-11-26 21:41:17,515: DEBUG - + echo '[###################.] > Reloading NGINX web server...'
  - 2021-11-26 21:41:17,515: DEBUG - + set -o xtrace
  - 2021-11-26 21:41:17,516: DEBUG - + ynh_systemd_action --service_name=nginx --action=reload
  - 2021-11-26 21:41:17,516: DEBUG - + local legacy_args=nalpte
  - 2021-11-26 21:41:17,516: DEBUG - + args_array=([n]=service_name= [a]=action= [l]=line_match= [p]=log_path= [t]=timeout= [e]=length=)
  - 2021-11-26 21:41:17,516: DEBUG - + local -A args_array
  - 2021-11-26 21:41:17,517: DEBUG - + local service_name
  - 2021-11-26 21:41:17,517: DEBUG - + local action
  - 2021-11-26 21:41:17,517: DEBUG - + local line_match
  - 2021-11-26 21:41:17,517: DEBUG - + local length
  - 2021-11-26 21:41:17,517: DEBUG - + local log_path
  - 2021-11-26 21:41:17,517: DEBUG - + local timeout
  - 2021-11-26 21:41:17,517: DEBUG - + ynh_handle_getopts_args --service_name=nginx --action=reload
  - 2021-11-26 21:41:17,517: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,517: INFO - [###################.] > Reloading NGINX web server...
  - 2021-11-26 21:41:17,637: DEBUG - + service_name=nginx
  - 2021-11-26 21:41:17,637: DEBUG - + action=reload
  - 2021-11-26 21:41:17,637: DEBUG - + line_match=
  - 2021-11-26 21:41:17,638: DEBUG - + length=20
  - 2021-11-26 21:41:17,638: DEBUG - + log_path=/var/log/nginx/nginx.log
  - 2021-11-26 21:41:17,638: DEBUG - + timeout=300
  - 2021-11-26 21:41:17,638: DEBUG - + '[' reload == stop ']'
  - 2021-11-26 21:41:17,638: DEBUG - + [[ -n '' ]]
  - 2021-11-26 21:41:17,638: DEBUG - + '[' reload == reload ']'
  - 2021-11-26 21:41:17,638: DEBUG - + action=reload-or-restart
  - 2021-11-26 21:41:17,639: DEBUG - + systemctl reload-or-restart nginx
  - 2021-11-26 21:41:17,868: DEBUG - + [[ -n '' ]]
  - 2021-11-26 21:41:17,869: DEBUG - + ynh_script_progression '--message=Upgrade of cryptpad completed' --last
  - 2021-11-26 21:41:17,869: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,949: DEBUG - + set +o xtrace
  - 2021-11-26 21:41:17,964: DEBUG - + echo '! Helper used in legacy mode !'
  - 2021-11-26 21:41:17,964: DEBUG - + set +x
  - 2021-11-26 21:41:17,967: DEBUG - + echo '[####################] > Upgrade of cryptpad completed'
  - 2021-11-26 21:41:17,967: DEBUG - + set -o xtrace
  - 2021-11-26 21:41:17,967: DEBUG - + ynh_exit_properly
  - 2021-11-26 21:41:17,967: DEBUG - + local exit_code=0
  - 2021-11-26 21:41:17,967: DEBUG - + rm -rf /var/cache/yunohost/download/
  - 2021-11-26 21:41:17,967: INFO - [####################] > Upgrade of cryptpad completed
  - 2021-11-26 21:41:17,968: DEBUG - + '[' 0 -eq 0 ']'
  - 2021-11-26 21:41:17,968: DEBUG - + exit 0
  - 2021-11-26 21:41:18,971: DEBUG - Checking that required services are up and running...
  - 2021-11-26 21:41:19,711: SUCCESS - cryptpad upgraded
metadata: 
  ended_at: 2021-11-26 21:41:19
  env: 
    BASH_XTRACEFD: 7
    NO_BACKUP_UPGRADE: 0
    YNH_APP_BASEDIR: /var/cache/yunohost/app_tmp_work_dirs/app_ax6o88mt
    YNH_APP_CURRENT_VERSION: 4.12.0~ynh1
    YNH_APP_ID: cryptpad
    YNH_APP_INSTANCE_NAME: cryptpad
    YNH_APP_INSTANCE_NUMBER: 1
    YNH_APP_MANIFEST_VERSION: 4.12.1~ynh1
    YNH_APP_UPGRADE_TYPE: UPGRADE_APP
    YNH_ARCH: amd64
    YNH_CWD: /var/cache/yunohost/app_tmp_work_dirs/app_ax6o88mt/scripts
    YNH_INTERFACE: cli
    YNH_STDRETURN: /tmp/tmp1y1np8wv/stdreturn
  error: None
  interface: cli
  operation: app_upgrade
  parent: None
  related_to: 
    - app
    - cryptpad
  started_at: 2021-11-26 21:35:27
  success: True
  yunohost_version: 4.3.3
metadata_path: /var/log/yunohost/categories/operation/20211126-213527-app_upgrade-cryptpad.yml
name: 20211126-213527-app_upgrade-cryptpad

From now I have delete the app and restore the pre-upgrade to get back and found my drive and datas. It was a bit complicated as my app was on an external disk volume. But the restore, back to the 4.12.0~ynh, is ok. I don't know what other logs I could found ???

Upgrade failed

Describe the bug

An error occured during the execution of te upgrade script.

Context

  • Hardware: desktop pc
  • YunoHost version: 4.2.6.1
  • I have access to my server: ssh and webmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
    • If yes, please explain:
  • Using, or trying to install package version/branch: master
  • If upgrading, current package version: 4.7.0

Steps to reproduce

  • If you performed a command from the CLI, the command itself is enough. For example: 
    sudo yunohost app upgrade

Expected behavior

Upgrade

Logs

https://paste.yunohost.org/raw/doculuqoru

Failed upgrade : NODEJS_VERSION: unbound variable

I'm getting the following error when I'm trying to upgrade Cryptpad v1.27 on Yunohost 3.4.2 :
./upgrade: line 50: NODEJS_VERSION: unbound variable

Here some context :

DEBUG name: cryptpad-pre-upgrade2
26207 DEBUG results:
26207 DEBUG   apps:
26207 DEBUG     cryptpad: Success
26208 DEBUG   system:
26208 DEBUG size: 98593948
26308 DEBUG + '[' 0 -eq 0 ']'
26309 DEBUG + grep -q cryptpad-pre-upgrade1
26309 DEBUG + sudo yunohost backup list
26710 DEBUG + sudo yunohost backup delete cryptpad-pre-upgrade1
27011 DEBUG + ynh_abort_if_errors
27012 WARNING ./upgrade: line 50: NODEJS_VERSION: unbound variable
27012 DEBUG + set -eu
27012 WARNING !!
27013 DEBUG + trap ynh_exit_properly EXIT
27013 WARNING   cryptpad's script has encountered an error. Its execution was cancelled.
27013 DEBUG ++ ynh_exit_properly
27013 WARNING !!
27014 DEBUG ++ local exit_code=1
27014 WARNING ./upgrade: line 42: ynh_backup_after_failed_upgrade: command not found
27015 DEBUG ++ '[' 1 -eq 0 ']'
27015 WARNING
27016 DEBUG ++ trap '' EXIT

installation script domain/path

On Readme we can read that "Installation is possible only on a root domain (CryptPad limitation)", but the installation script ask for a path and doesn't use it.

It's not a serious problem but we can be disturbed…

Thanks !

Include installMethod property in server telemetry

Describe the bug

I don't necessarily consider this a bug, but rather a way for you (the YunoHost-CryptPad package maintainers) to help us (the CryptPad core development team) to provide a safer platform.

The short version

Please set the installMethod property of the nodejs server's config file to a custom string indicating that the server was installed via YunoHost.

The detailed version

By default, the CryptPad server sends some telemetry to a server that our team administrates at launch time and every 24 hours thereafter. The complete details of the telemetry are logged by the server whenever they are sent. In case you were unaware or are curious about what is shared with our team you can search the node server's logs with grep SERVER_TELEMETRY /path/to/your/logs/*.

Most of the time we only pay attention to the number of unique IPs that send this telemetry. This counts in our favour when we write grant proposals that indicate how widely the software is used.

Recently we've been trying to engage administrators to encourage them to:

  1. update to recent versions of the software so that we can be more proactive about disclosing security flaws and improvements
  2. use the available self-diagnostic features to configure their instance securely (as referenced in #98)

During some periodic reviews of this telemetry data we noticed some patterns, like relatively large numbers of instances running particular (outdated) versions of the platform. We suspect this is a result of third-party packages or install scripts hardcoding those versions. Our 4.8.0 release added an installMethod property to this server telemetry. By default this has a value of unspecified. This PR to the community-maintained docker repo set custom strings (docker, docker-alpine) for variants of the docker config files.

Including this value in telemetry would help us identify or rule out YunoHost as a source of commonly misconfigured instances and work with you to fix avoidable errors in the future, if necessary.

Context

I am the project lead for the CryptPad platform and it would be helpful to be able to easily identify which third-party instances were installed via YunoHost.

Steps to reproduce

  1. Launch a CryptPad server running 4.8.0 or later
  2. scan its logs for a line including the string SERVER_TELEMETRY
  3. determine whether the JSON included in this line contains the string 'unpecified' or a custom YunoHost-specific value.

Expected behavior

  • CryptPad instances installed using YunoHost provide a value in their telemetry data that allows the project's core developers to distinguish them from instances installed via alternative methods

Logs

["INFO","2021-08-17T05:48:06.706Z","SERVER_TELEMETRY",{"version":"4.10.0","installMethod":"this should say YunoHost","httpUnsafeOrigin":"http://localhost:3000","adminEmail":"[email protected]","consentToContact":true,"instancePurpose":"experiment"}]

502 bad gateway on raspberry pi 3

Hello !
I tried to install cryptpad on my RPI3. Everythink looked fine during the install but I can't access the app…
The content of /var/log/cryptpad/cryptpad.log isn't much help (for me anyway) :

loading task scheduler

[2018-03-28T08:22:13.584Z] server available http://[::]:3000
Cryptpad is customizable, see customize.dist/readme.md for details

Thanks for the help !

several problems with the new version

Describe the bug
fresh installation because the upgrade of last night failed and I could not restore the installation.
Maybe I'm wrong but at level 7 the cryptpad should recognize the accounts installed on the system no?
For me it does not.
I can't also load the /admin section. It hangs a load shared folder. I've tested on multiple hosts, multiple browsers.

Any ideas on how to debug this?

Versions

  • Hardware: VM on i7 4vcore 12GB ...
  • YunoHost version: 4.1.8

Error during install

How to post a meaningful bug report

  1. Read this whole template first.
  2. Determine if you are on the right place:
    • If you were performing an action on the app from the webadmin or the CLI (install, update, backup, restore, change_url...), you are on the right place!
    • Otherwise, the issue may be due to the app itself. Refer to its documentation or repository for help.
    • When in doubt, post here and we will figure it out together.
  3. Delete the italic comments as you write over them below, and remove this guide.

Describe the bug

I'm unable to install app

Context

  • Hardware: VPS bought online
  • YunoHost version: 4.2.8.2
  • I have access to my server: Through SSH | through the webadmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: default

Steps to reproduce

  • If you performed a command from the CLI, the command itself is enough. For example: 
    sudo yunohost app install --debug cryptpad

Expected behavior

I expected Cryptpad to be installed

Logs

https://paste.yunohost.org/raw/enesacuxim

not same permissions on fresh install vs upgraded version

Describe the bug

*I have an app upgraded from oldest version and one fresh install, the two are working, but the folders permissions are quiet diferents *

Context

  • Hardware: *VPS bought online & Old laptop or computer *
  • YunoHost version: 11.1.17
  • I have access to my server: Through SSH | through the webadmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
    I have restore my app few times on the vps server
  • Using package version/branch: 5.2.1~ynh8

Steps to reproduce

I am trying understand why I have few different permissions between an instance Cryptpad upgraded and another fresh install…

On the server with the Cryptpad upgraded from older version on vps

ls -l /var/www/cryptpad

-rw-rw----   1 cryptpad www-data  44825 Dec 21 15:34 and_so_it_begins.png
drwxr-x---  67 cryptpad www-data   4096 Apr  1 10:28 blob
drwxr-x---  20 cryptpad www-data   4096 Mar 16 08:24 block
-rw-rw----   1 cryptpad www-data   1365 Dec 21 15:34 bower.json
-rw-rw----   1 cryptpad www-data 399414 Dec 21 15:34 CHANGELOG.md
-rw-rw----   1 cryptpad www-data   3351 Dec 21 15:34 CODE_OF_CONDUCT.md
drwxrwx---   2 cryptpad www-data   4096 Apr  1 10:11 config
-rw-rw----   1 cryptpad www-data 202130 Dec 21 15:34 cryptofist.png
drwxrwx---   3 cryptpad www-data   4096 Apr  1 10:25 customize
drwxrwx---   8 cryptpad www-data   4096 Dec 21 15:34 customize.dist
drwxrwx---  10 cryptpad www-data   4096 Feb 13 21:12 customize.old
drwxr-x---   8 cryptpad www-data   4096 Nov 11  2021 data
drwxr-x--- 226 cryptpad www-data   4096 Apr  1 07:44 datastore
drwxrwx---   2 cryptpad www-data   4096 Dec 21 15:34 docs
drwxrwx---   6 cryptpad www-data   4096 Dec 21 15:34 lib
-rw-rw----   1 cryptpad www-data  34520 Dec 21 15:34 LICENSE
drwx------   2 cryptpad www-data   4096 Nov 11  2021 lost+found
drwxrwx--- 284 cryptpad www-data  12288 Feb 13 20:39 node_modules
-rw-rw----   1 cryptpad www-data   1955 Dec 21 15:34 package.json
-rw-rw----   1 cryptpad www-data 246864 Mar 31 22:02 package-lock.json
-rw-rw----   1 cryptpad www-data   5509 Dec 21 15:34 readme.md
-rw-rw----   1 cryptpad www-data 127697 Dec 21 15:34 screenshot.png
-rw-rw----   1 cryptpad www-data 211678 Dec 21 15:34 screenshot-suite.png
drwxrwx---   5 cryptpad www-data   4096 Dec 21 15:34 scripts
-rw-rw----   1 cryptpad www-data  13413 Dec 21 15:34 server.js
-rw-rw----   1 cryptpad www-data      0 Sep  9  2021 temp.md
drwxrwx---  39 cryptpad www-data   4096 Dec 21 15:34 www

On the server with a fresh install in home server:

-rw-rw----   1 cryptpad www-data  44825 21 déc.  15:34 and_so_it_begins.png
drwxr-xr-x   4 cryptpad www-data   4096  2 avril 16:44 blob
drwxr-xr-x   3 cryptpad cryptpad   4096  2 avril 16:47 block
-rw-rw----   1 cryptpad www-data   1365 21 déc.  15:34 bower.json
-rw-rw----   1 cryptpad www-data 399414 21 déc.  15:34 CHANGELOG.md
-rw-rw----   1 cryptpad www-data   3351 21 déc.  15:34 CODE_OF_CONDUCT.md
drwxrwx---   2 cryptpad www-data   4096  2 avril 16:47 config
-rw-rw----   1 cryptpad www-data 202130 21 déc.  15:34 cryptofist.png
drwxr-xr-x   3 cryptpad www-data   4096  2 avril 16:37 customize
drwxrwx---   8 cryptpad www-data   4096 21 déc.  15:34 customize.dist
drwxr-xr-x   8 cryptpad www-data   4096  2 avril 16:37 data
drwxr-xr-x   7 cryptpad www-data   4096  2 avril 16:44 datastore
drwxrwx---   2 cryptpad www-data   4096 21 déc.  15:34 docs
drwxrwx---   6 cryptpad www-data   4096 21 déc.  15:34 lib
-rw-rw----   1 cryptpad www-data  34520 21 déc.  15:34 LICENSE
drwxr-xr-x 284 cryptpad www-data  12288  2 avril 16:37 node_modules
-rw-rw----   1 cryptpad www-data   1955 21 déc.  15:34 package.json
-rw-rw----   1 cryptpad www-data 246864  2 avril 16:37 package-lock.json
-rw-rw----   1 cryptpad www-data   5509 21 déc.  15:34 readme.md
-rw-rw----   1 cryptpad www-data 127697 21 déc.  15:34 screenshot.png
-rw-rw----   1 cryptpad www-data 211678 21 déc.  15:34 screenshot-suite.png
drwxrwx---   5 cryptpad www-data   4096 21 déc.  15:34 scripts
-rw-rw----   1 cryptpad www-data  13413 21 déc.  15:34 server.js
drwxrwx---  39 cryptpad www-data   4096  2 avril 16:37 www

So I am not quiet, with some permissions and owners different for
the folders blob, block, data, datastore and node_modules

Why on a fresh install the permissions seems be drwxr-xr-x and on my older instance seems be drwxrwx--- ??

And why n a fresh install the folder block owners are cryptpad:cryptpad but on the older one are cryptpad:www-data ??

Expected behavior

Do I need try change the permissions ans owners on the upgraded app to have the same permissions as on the fresh install ?
What is the better to do ?

Upgrade failed

Describe the bug

upgrade to 5.2.1~ynh5 failed

Context

  • Hardware: *VPS bought online *
  • YunoHost version: 11.1.13
  • I have access to my server: *Through SSH *
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: * yes*
    • If yes, please explain: have move some folders in differents volumes
  • Using, or trying to install package version/branch: stable
  • If upgrading, current package version: 5.2.1~ynh4

Steps to reproduce

  • If you performed a command from the CLI, the command itself is enough. For example: 
    sudo yunohost app upgrade cryptpad

The upgrade failed and also the restore...

To restore the backup app I have to delete the folder /var/www/cryptpad, I have to create the domain sandbox-cryptpad.mydomain.tld and the the cert install. When finally I could restore the backup, the file /etc/nginx/conf.d/sandbox-cryptpad.mydomain.tld/cryptpad.conf wasn't here, so I have to do a cp -a /etc/nginx/conf.d/cryptpad.mydomain.tld/cryptpad.conf /etc/nginx/conf.d/sandbox-cryptpad.mydomain.tld/....

Not easy...

Expected behavior

just an upgrade of the instance cryptpad, or if the upgrade failed a clean restore

Logs

yunohost tools upgrade apps
Info: The following apps will be upgraded: cryptpad, grav, grav__2
Info: Now upgrading cryptpad...
Info: [....................] > Loading installation settings...
Info: [....................] > Checking version...
Info: [....................] > Backing up the app before upgrading (may take a while)...
Info: [....................] > Stopping a systemd service...
Info: [+...................] > Ensuring downward compatibility...
Info: [#...................] > Making sure dedicated system user exists...
Info: [#...................] > Setting up sandobx domain: sandbox-cryptpad.linux07.fr
Warning: The domain already exists
Warning: [Error] Upgrade failed.
Warning: rm: cannot remove '/var/www/cryptpad': Device or resource busy
Warning: 19590 Could not restore cryptpad: Something unexpected went wrong:
Warning: Traceback (most recent call last):
Warning:   File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 1465, in _restore_app
Warning:     permission_create(
Warning:   File "/usr/lib/python3/dist-packages/yunohost/log.py", line 410, in func_wrapper
Warning:     result = func(*args, **kwargs)
Warning:   File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 450, in permission_create
Warning:     permission_url(
Warning:   File "/usr/lib/python3/dist-packages/yunohost/log.py", line 410, in func_wrapper
Warning:     result = func(*args, **kwargs)
Warning:   File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 546, in permission_url
Warning:     ur = _validate_and_sanitize_permission_url(ur, app_main_path, app)
Warning:   File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 926, in _validate_and_sanitize_permission_url
Warning:     _assert_domain_exists(domain)
Warning:   File "/usr/lib/python3/dist-packages/yunohost/domain.py", line 186, in _assert_domain_exists
Warning:     raise YunohostValidationError("domain_unknown", domain=domain)
Warning: yunohost.utils.error.YunohostValidationError: Domain 'sandbox-cryptpad.linux07.fr' unknown
Warning: 22536 Nothing was restored
Warning: Uhoh ... Yunohost failed to restore the app to the way it was before the failed upgrade :|
Error: Could not upgrade cryptpad: An error occurred inside the app upgrade script
Info: The operation 'Upgrade the 'cryptpad' app' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20230304-152457-app_upgrade-cryptpad' to get help
Warning: Here's an extract of the logs before the crash. It might help debugging the error:
Info: INFO - [#...................] > Making sure dedicated system user exists...
Info: DEBUG - + ynh_system_user_create --username=cryptpad --home_dir=/var/www/cryptpad
Info: DEBUG - + use_shell=0
Info: DEBUG - + home_dir=/var/www/cryptpad
Info: DEBUG - + groups=
Info: DEBUG - + ynh_system_user_exists cryptpad
Info: DEBUG - + getent passwd cryptpad
Info: DEBUG - + '[' UPGRADE_PACKAGE == UPGRADE_APP ']'
Info: DEBUG - + chgrp -R www-data /var/www/cryptpad
Info: DEBUG - + [[ cryptpad.linux07.fr == *\.* ]]
Info: DEBUG - + sandboxdomain=sandbox.cryptpad.linux07.fr
Info: DEBUG - + [[ cryptpad.linux07.fr == *\.*\.* ]]
Info: DEBUG - + sandboxdomain=sandbox-cryptpad.linux07.fr
Info: DEBUG - + [[ cryptpad.linux07.fr == *\.\l\o\c\a\l ]]
Info: INFO - [#...................] > Setting up sandobx domain: sandbox-cryptpad.linux07.fr
Info: DEBUG - + '[' -n sandbox-cryptpad.linux07.fr ']'
Info: DEBUG - + yunohost domain add sandbox-cryptpad.linux07.fr
Info: DEBUG - attribute 'virtualdomain' with value 'sandbox-cryptpad.linux07.fr' is not unique
Info: WARNING - The domain already exists
Info: DEBUG - + ynh_exit_properly
Error: The app 'cryptpad' failed to upgrade, and as a consequence the following apps' upgrades have been cancelled: cryptpad, grav, grav__2
Warning: unable to upgrade apps: The operation 'Upgrade the 'cryptpad' app' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20230304-152457-app_upgrade-cryptpad' to get help
Error: Some apps could not be upgraded

Few logs here...

log upgrade failed

20230304-152457-app_upgrade-cryptpad.log
https://paste.yunohost.org/raw/fejevaveze

20230304-152736-app_remove-cryptpad.log
https://paste.yunohost.org/raw/epewupeluv

20230304-152458-backup_create.log
https://paste.yunohost.org/raw/dumoyapejo

20230304-152736-app_remove-cryptpad.log
https://paste.yunohost.org/raw/ivawumawet

20230304-152740-domain_remove-sandbox-cryptpad.linux07.fr.log
https://paste.yunohost.org/raw/afozozopis

20230304-152807-permission_delete-cryptpad.log
https://paste.yunohost.org/raw/zipohozoro

Broken Cryptpad after 1.15.0 upgrade

After updating the app to 1.15.0, I can open cryptdrive
But when I try to open a pad (text) I get

Cannot GET /pad/undefined/pad/inner.html?ver=1.12.0

The same error appears with the editing or the read only link.

I just install cryptpad with yunohost package 5 days ago and this is my first upgrade.
I did upgrade with yunohost app upgrade --verbose -u https://github.com/YunoHost-Apps/cryptpad_ynh cryptpad

During upgrade, I received few warnings :

Attention : 2017-09-14 18:57:35 URL:https://codeload.github.com/xwiki-labs/cryptpad/tar.gz/v1.15.0 [7890094] -> "app.tar.gz" [1]
Attention : npm WARN [email protected] No repository field.
Attention : npm WARN [email protected] No license field.
Attention :
up to date in 3.203s
Attention : bower bootstrap#~3.1.1 invalid-meta The "main" field cannot contain font, image, audio, or video files
Attention : bower bootstrap#~3.1.1 invalid-meta The "main" field cannot contain font, image, audio, or video files
Attention : bower bootstrap#~3.1.1 invalid-meta The "main" field cannot contain font, image, audio, or video files
Attention : bower bootstrap#~3.1.1 invalid-meta The "main" field cannot contain font, image, audio, or video files

How can I repair my CryptPad install ?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.