Describe the bug

Hey, I tried to install Misskey, but it failed. It was just to check out, so no biggy, but I thought I should at least report it anyways.

Context

• Hardware: Old laptop
• YunoHost version: 4.2.6.1
• I have access to my server: Through SSH and through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • If yes, please explain: N/A
• Using, or trying to install package version/branch: trying to install misskey
• If upgrading, current package version: N/A

Steps to reproduce

```sh
sudo su -
yunohost app install misskey
```

Expected behavior

It installs :)

Logs

ynh log: https://paste.yunohost.org/raw/cemewocaci

npm log:

root@spectraltheorem:~# cat /root/.npm/_logs/2021-08-02T18_11_56_868Z-debug.log 
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/opt/node_n/n/versions/node/12.22.4/bin/node',
1 verbose cli   '/opt/node_n/n/versions/node/12/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build-webpack'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild-webpack', 'build-webpack', 'postbuild-webpack' ]
5 info lifecycle [email protected]~prebuild-webpack: [email protected]
6 info lifecycle [email protected]~build-webpack: [email protected]
7 warn lifecycle The node binary used for scripts is /tmp/yarn--1627927911645-0.8918027157145176/node but npm is using /opt/node_n/n/versions/node/12.22.4/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
8 verbose lifecycle [email protected]~build-webpack: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~build-webpack: PATH: /opt/node_n/n/versions/node/12.22.4/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/misskey/node_modules/.bin:/tmp/yarn--1627927911645-0.8918027157145176:/var/www/misskey/node_modules/.bin:/usr/local/share/.config/yarn/link/node_modules/.bin:/opt/node_n/n/versions/node/12.22.4/libexec/lib/node_modules/npm/bin/node-gyp-bin:/opt/node_n/n/versions/node/12.22.4/lib/node_modules/npm/bin/node-gyp-bin:/opt/node_n/n/versions/node/12.22.4/bin/node_modules/npm/bin/node-gyp-bin:/opt/node_n/n/versions/node/12/bin:/opt/node_n/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle [email protected]~build-webpack: CWD: /var/www/misskey
11 silly lifecycle [email protected]~build-webpack: Args: [ '-c', 'webpack' ]
12 silly lifecycle [email protected]~build-webpack: Returned: code: 2  signal: null
13 info lifecycle [email protected]~build-webpack: Failed to exec build-webpack script
14 verbose stack Error: [email protected] build-webpack: `webpack`
14 verbose stack Exit status 2
14 verbose stack     at EventEmitter.<anonymous> (/opt/node_n/n/versions/node/12.22.4/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack     at EventEmitter.emit (events.js:314:20)
14 verbose stack     at ChildProcess.<anonymous> (/opt/node_n/n/versions/node/12.22.4/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack     at ChildProcess.emit (events.js:314:20)
14 verbose stack     at maybeClose (internal/child_process.js:1022:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
15 verbose pkgid [email protected]
16 verbose cwd /var/www/misskey
17 verbose Linux 4.19.0-17-amd64
18 verbose argv "/opt/node_n/n/versions/node/12.22.4/bin/node" "/opt/node_n/n/versions/node/12/bin/npm" "run" "build-webpack"
19 verbose node v12.22.4
20 verbose npm  v6.14.14
21 error code ELIFECYCLE
22 error errno 2
23 error [email protected] build-webpack: `webpack`
23 error Exit status 2
24 error Failed at the [email protected] build-webpack script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 2, true ]
root@spectraltheorem:~# 

Hello! Sorry for my english!
I tried install misskey, but I see error:
Error: Command failed with exit code 134: npm run build
2022-07-14 13:14:50,462: DEBUG - at makeError (/var/www/misskey/node_modules/execa/lib/error.js:60:11)
Help me please!

Describe the bug

A successful backup of Misskey cannot be performed.

Context

• Hardware: Old computer
• YunoHost version: 11.1.15
• 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: 12.119.2~ynh1

Steps to reproduce

I'm trying to perform a backup of Misskey. First, I tried to use the webadmin and it seems to have locked up the webadmin. Then, I went to the terminal and tried to back up Misskey using yunohost backup create --apps misskey. It tries to do the backup, but ultimately fails with this wording:
_Error: Could not add the files '/var/www/misskey' (named in the archive 'apps/misskey/backup/var/www/misskey') to be backed up into the compressed archive '/home/yunohost.backup/archives/20230331-025254.tar'
Info: The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20230331-025254-backup_create' to get help
Error: Could not create the backup archive
_

Expected behavior

I would expect a successful backup to be performed. I would then be able to access the backup from the webadmin and download the backup.

What actually happens, is there seems to be a backup file created if I use the terminal to view the folder at dir /home/yunohost.backup/archives, but there is no .json file. The webadmin then takes several hours to populate the backup section or sometimes times out with a 504 Timeout. I can successfully backup other apps.
I have tried to back up Misskey several times and I get the same result. There will be 20+gb .tar files created, but no .json file. There is over 100gb of storage left on my drive. I have deleted several of the failed attempts in order to create space for a successful backup.

Logs

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

Misskey is currently on a pretty old version and has been updated a lot. The auto update branches don't seem to work. Is there any plans to update the main branch?

misskey fails to update. here's the log:

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

I believe this is due to this module not being found:

Module not found: Error: Can't resolve 'crc-32' in '/var/www/misskey/packages/client/src/pages/reversi'
[...]
webpack 5.70.0 compiled with 1 error and 39 warnings in 78321 ms
[...]
Error: Command failed with exit code 1: npm run build

Also there are lots of error messages before. I'm not sure what's happening there.

affected: 12.108.1~ynh2 and 12.109.2~ynh1 (i'm currently (stuck) on 12.102.1~ynh1)

This is just a quick discussion I wanted to open about this package. First: Thank you for making misskey so easily accessiable with yunohost.

basically I would like to ask if it would be possible to allow the exclusion of certain folders in the backup script via a config-flag perhaps. Maybe something like described here: https://yunohost.org/ar/backup/include_exclude_files#do-not-backup-large-amounts-of-data

There should be an option to exclude misskeys "files" directory when updating, since it can get quite large with time (mine is about 40GB right now) making updating a slow and tedious process to deal with.

Is there something I can do so the files directory does not get backed up when updating misskey via the package?

First, thanks for the good work and the quick update to v 12.108.1.

Everything seems to be working proper, except a flashing message "DEV BUILD" in the top left corner on all pages.

Fix the autoupdater. Source file seems not to be updated.

Describe the bug

I'm unable to install misskey at all on the latest ynh version

Context

• Hardware: VM on Proxmox. 1 CPU (2 cores) and 6 GB of RAM
• YunoHost version: 4.2.5.2 (stable and latest atm)
• I have access to my server: Through SSH, through the webadmin, direct access via keyboard / screen but the webmin for this attempt of install
• 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 atm

Steps to reproduce

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

  sudo yunohost app install misskey

• If you used the webadmin, please perform the equivalent command from the CLI first.
• If the error occurs in your browser, explain what you did:
  1. Go to 'Application'
  2. Click on 'Install'
  3. Search for 'Misskey'
  4. Click on 'Install'
  5. Choose 'test.example.TLD'
  6. Wait the installation process
  7. See the error

Expected behavior

Misskey to be installated on the selected domain name.

Logs

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

Changed dependencies:

• Node.js 18.x or later
• PostgreSQL 15.x
• Migrated from Yarn to pnpm

https://misskey-hub.net/en/docs/releases.html#_13-0-0

Environment:

1. Win10
2. Brave Desktop v1.46.134, (Chromium to 108.0.5359.94)
3. Yunohost Misskey 12.119.0~ynh1

Steps:

1. Log in to your user account;
2. Go to profile settings, at: https://$instance.tld/settings/profile
   Click on the button responsible for the "Change avatar" function
3. Select a photo.

Expected result: the photo is uploaded to the user's drive and set as an avatar;

Actual result: the photo is uploaded to the user's drive, but the avatar is not changed and remains in the "eternal download.

Hi! A friend just installed Misskey through Yunohost and wasn't aware of needing to edit the configuration file to work with instances that have authorized fetch enabled. I wrote up directions on doing the edits and thought it would be really helpful to at least note in the readme that it must be done or federation with some instances will not work.

Here are the directions I wrote: https://gist.github.com/elenners/d7af0b6cf64719d7407c4aad03eb43b1

Thank you!

Hi there,

I wanted to install Misskey on the latest stable, but I do get:
INFO * [core boot] Welcome to Misskey!
INFO * [core boot] Misskey v12.110.0
INFO * [core boot env] NODE_ENV: production
INFO * [core boot env] You do not have root privileges
INFO * [core boot nodejs] Version v16.13.1 detected.
ERR * [core boot nodejs] At least Node.js v16.14.0 required!
INFO * [core] The process is going to exit with code 1

What could I do?

Regards,

Stefan

Hello, I'm DignifiedSilence. Misskey contributor.
I have several suggestions below to improve this repo's README.

1. In the section of "Screenshots", its image( screenshot of web client ) is came from Misskey v11 or v10. It needs to be replaced by a new one.

2. In the section of "Documententation and resources", Official app website: https://join.misskey.page is an old one. The new Misskey official website is https://misskey-hub.net/ .

3. "misskey.io" isn't Misskey official instance and not related to Misskey project. In my opinion, the new Misskey official website is recommended in About.

Is there any reason to back up first, and stop the service afterwards?

Misskey isn’t as static as other apps. Backup takes some time and meanwhile there are a lot of unimportant posts, but sometimes important like follow request and private messages too, which then vanish into nothing.

Does it make sense to manually stop the service first?

Hi there,

what settings I should use when enabling the E-Mail-Server inside Misskey? When using the mailsystem from yunohost (smtp adress, port 587, no authentication) it doesn't seem to work. When using another server outside yunohost it works. But it would make sense to use the yunohost server.

Error message:
Internal error occurred. Please contact us if the
error persists.
5d37dbcb-891e-41ca-a3d6-e690c97775ac

Regards,

Stefan

After some time running the server, I always get remaining connection slots are reserved for non-replication superuser connections error. This only happens with YunoHost install...

Using: YunoHost 11.2.3
Used the Gui to install: Misskey version 12.119.2~ynh1
can access console via: DigitalOcean (Debian 11 x64)

just wondering if there's a way to manually upgrade to a more recent version of Misskey!
I saw talks of it maybe or maybe not being possible depending on the version of Yunohost that is used and I'm a bit overwhelmed looking through things. I'm fairly new to all of this, so apologies for not being super detailed in this post!

Thank you for your time and help.

Describe the bug

I logged into Yunohost and updated my packages. There was also an update for Misskey so I chose to install it. It hung on the app backup step and I let it sit for well over an hour. I hard refreshed the page and then when it didn't load I restarted the server.

Upon reboot, I get the error pop up below when I go into the Updates section, and Misskey is no longer showing in the installed application list. The site is still up though.

Context

• Hardware: Contabo VPS on Debian 10
• YunoHost version: 4.3.6.3
• 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?: No
  • If yes, please explain: --
• Using, or trying to install package version/branch: Misskey 12.110.1~ynh2
• If upgrading, current package version: 12.110.1~ynh1

Steps to reproduce

1. Go to Updates page
2. Click on Install for Misskey
3. The window showing the progress will display and get stuck on backing up app
4. See error after restart

Expected behavior

The Misskey update should have completed and been applied successfully. The app should still display as an installed application.

Logs

https://paste.yunohost.org/raw/ekonaqugap - apparently the update was successful so it's odd

Describe the bug

Error when updating Misskey from version 12.119.2~ynh1 to latest.

The webadminUI reports HTTP code 500 on "PUT" /yunohost/api/apps/misskey/upgrade

It seems that the update is then canceled. Misskey then fail to restore, and can't be rerun.

Context

• Hardware: VPS at OVH, uname : Linux <host> 5.10.0-27-cloud-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64 GNU/Linux, no modification other than installing Yunohost via official installation instructions (with Misskey, Dokuwiki, Roundcube)
• YunoHost version: 11.2.11.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
• If upgrading, current package version: 12.119.2~ynh1

Steps to reproduce

Before upgrading misskey, I updated my apt packages successfully.

• Upgrade Misskey application, from WebAminUI or from CLI (sudo yunohost app upgrade <id>)
  Logs from CLI at ticket's end.

(had to create misskey log directory for CLI upgrade to work properly)

Logs

WebAdminUI log paste : https://paste.yunohost.org/raw/qahazilezo
CLI log paste : https://paste.yunohost.org/raw/itewocenor

Is Misskey no longer supported? The current version that can be installed with YunoHost is 12.119.2.

There is now version 2023.12.2, which means that there are over 180 version updates (including beta versions and release candidates) and a year(!) of further development and bug fixing between the YunoHost version and the official version!

Is there any hope that the software will still be updated?

I have misskey 12.110.0-ynh2 installed in a dedicated domain.
can't upload files larger than 1M

nginx log :
2022/04/23 14:00:00 [error] 3659#3659: *238991 client intended to send too large body: 1996918 bytes, client: 197.xxx.xxx.xxx, server: friends.domain.me, request: "POST /api/drive/files/create HTTP/2.0", host: "friends.domain.me", referrer: "https://friends.domain.me/"
@memo-567

I am a little new to Yuno and would like to use Misskey. The log is attached.
misskey_script_error.txt

Misskey write a lot of cache files for yarn and node_modules, up to 3GB after a fresh install.
I suppose this could not be backed up, as it would rebuilt it anyway ?
Then we should exclude it from the backup.

This could be coupled with #58.

I'd be happy to test this is someone does it :)

Misskey upgrade fails on productive server (Debian 10 Buster), but not on test server (VirtualBox test environment).

[Error] Upgrade failed.
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
This action broke dpkg/APT (the system package managers)... You can try to solve this issue by connecting through SSH and running `sudo apt install --fix-broken` and/or `sudo dpkg --configure -a`.

No changes after runnig 'sudo apt install --fix-broken': 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
and 'sudo dpkg --configure -a'

Second upgrade also fails.

Logfile: https://paste.yunohost.org/raw/olidifival

It is not possible to enter an email address neither when registering nor after registering with an invitation code.

The reason is an upgrade to linux-image-4.19.0-20-amd64.

"This will be fixed in the next release" the developer told me:

https://forum.misskey.io/d/93-unable-to-add-mail-adress

So, don't upgrade if not necessary!

The next release will be very important to all who did already - like me 🙄