Sharkey broken installation

What app is this about, and its version: Sharkey 2025.4.4
What YunoHost version are you running: latest
What type of hardware are you using: VPS bought online

Describe your issue

hello! this is the first time since I started using YunoHost that I’m running into installation problems.

I tried to install Sharkey 5 times in two days but I always run into the same issue: confirmation in the logs that the Sharkey installation is complete… but then when I try to access the URL I see the Sharkey logo for a second and then the page becomes blank.

If I go to Developer Tools and see the page code I can spot the sharkey logo and info. If I add /login/ to my domain I see a Sharkey login dialogue for my instance but the YunoHost admin username doesn’t work.

I checked the YunoHost detailed logs and noticed that there is a new admin user created called “sharkey” during installation, but that also doesn’t work if I enter it in the login page.

I’m a little bit lost because when attempting to install Sharkey there is no input anywhere that says which user should be the admin or a password… no background info on the first account created…

Any help would be very much appreciated! (I uninstalled it so can’t point to the instance… just wondering if people had the same problem).

Share relevant logs or error messages

I uninstalled Sharkey because it was causing all sorts of issues

Hello @ele

That’s clearly not the expected behaviour: first time accessing the URL leads to a page that allows the creation of an admin user.
Did you check the sharkey’s logs (webadmin > tools > services > sharkey) ?

Thanks. I just attempted to install it for the 7th time… same result.

Here are my logs: https://paste.yunohost.org/raw/paruxadena

Any insights would be greatly appreciated

could you share the journalctl and sharkey logs ?

here we go (sorry the log paste didn’t work, I had to copy and paste)

|INFO *|[core boot]||Welcome to Sharkey!|
|---|---|---|---|
|INFO *|[core boot]||Sharkey v2025.4.4|
|INFO *|[core boot env]||NODE_ENV: production|
|INFO *|[core boot nodejs]||Version v22.21.0 detected.|
|INFO *|[config]||Reading configuration from /var/www/sharkey/.config/default.yml|
|INFO *|[core boot config]||Loaded|
|INFO *|[core boot]||Sharkey initialized|
|INFO *|[core boot]||mode: [disableClustering: false, onlyServer: false, onlyQueue: false]|
|INFO *|[core nest]||NestFactory: Starting Nest application...|
|INFO *|[core nest]||InstanceLoader: MainModule dependencies initialized|
|INFO *|[core nest]||InstanceLoader: QueueModule dependencies initialized|
|INFO *|[db sql]||No classes were found using the provided glob pattern:  ../../migration/*.js|
|INFO *|[core nest]||InstanceLoader: RepositoryModule dependencies initialized|
|INFO *|[core nest]||InstanceLoader: GlobalModule dependencies initialized|
|INFO *|[SearchService]||-- Provider: sqlLike|
|INFO *|[core nest]||InstanceLoader: DaemonModule dependencies initialized|
|INFO *|[core nest]||InstanceLoader: CoreModule dependencies initialized|
|INFO *|[core nest]||InstanceLoader: EndpointsModule dependencies initialized|
|INFO *|[core nest]||InstanceLoader: ServerModule dependencies initialized|
|INFO *|[core boot]||Starting 1 worker...|
|INFO *|[activity-log-cleanup]||Activity Log cleanup complete; removed 0 expired logs.|
|INFO 1|[config]||Reading configuration from /var/www/sharkey/.config/default.yml|
|INFO 1|[core]||Start worker process... pid: 37285|
|INFO 1|[config]||Reading configuration from /var/www/sharkey/.config/default.yml|
|INFO 1|[core nest]||NestFactory: Starting Nest application...|
|INFO 1|[core nest]||InstanceLoader: QueueModule dependencies initialized|
|INFO 1|[db sql]||No classes were found using the provided glob pattern:  ../../migration/*.js|
|INFO 1|[core nest]||InstanceLoader: RepositoryModule dependencies initialized|
|INFO 1|[core nest]||InstanceLoader: GlobalModule dependencies initialized|
|INFO 1|[SearchService]||-- Provider: sqlLike|
|INFO 1|[core nest]||InstanceLoader: CoreModule dependencies initialized|
|INFO 1|[core nest]||InstanceLoader: QueueProcessorModule dependencies initialized|
|INFO *|[core boot]||All workers started|
|INFO *|[core boot]||Now listening on 0.0.0.0:23350 on https://URL REDACTED|
|INFO 1|[queue check-expired-mutings]||Checking expired mutings...|
|INFO 1|[queue check-expired-mutings]||All expired mutings checked.|
|INFO 1|[queue check-expired-mutings]||Checking expired mutings...|
|INFO 1|[queue check-expired-mutings]||All expired mutings checked.|
|INFO *|[activity-log-cleanup]||Activity Log cleanup complete; removed 0 expired logs.|

That’s a fork of misskey. I just reproduced your issue. Add visitors permission to sharkey and it will work right away.
I remember having had the same issue with misskey (a while ago). Don’t know why, I didn’t investigate.

1 Like

It worked!!! Thank you SO MUCH!!!

@ jarod5001 if I may ask a quick follow-up question: the signup screen shows a prompt for “initial password for setup” - in addition to a username and password. I tried to keep it blank as it says, but I keep getting error messages that I cannot create the user. I wonder if you have recommendations as to what should I put there?

Sadly, I don’t use it, so I can’t help with this issue.

Thanks though. I tried using my YunoHost password and got an error message… then I saw the instance listed 1 user. Tried the username I had initially put… but none of the passwords I had used work and there’s no option to use the “forgot password?” and reset it via email. I’m this close to giving up on Sharkey, sadly

I’m answering my own question to close up this topic.

So the thing that worked in the create an account screen was leaving the first password field blank… adding any kind of username and then using the YunoHost instance password as the password for the account.

I managed to get it running for a day… but I turned on 2FA and the next time I had to log in, I got an error message when entering the 2FA code. Ditto for recovery codes, so I finally gave up on Sharkey :smiling_face_with_tear:

You can share screenshots and logs to help fix it

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.