Initial lemmy setup fails

My YunoHost server

Hardware: Hetzner cloud
YunoHost version: 11.0.9.5 (stable)
I have access to my server : both
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Installing lemmy worked without a problem, but when I visit the site for the first time I’m asked to “Set Up Site Administrator”. When I create a new user this way I am next asked to set up the lemmy instance, but when I try to save it says “not an admin”.
When I do all that with the credentials I was sent per email it says “user already exists” in the first step and when I try to login I get a 404 error.

I tried to find a way to setup the site via ssh but didn’t succeed either.

1 Like

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

We needs logs of your Lemmy instance, and the resource address that gives out a 404 error.

1 Like

This is what happens if I try to log in here.

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). moz-extension:33:9
httpbase: https://climatejustice.community client.js:2:930676
wsUri: wss://climatejustice.community/api/v3/ws client.js:2:930705
isHttps: true client.js:2:930731
No JWT cookie found. client.js:2:933009
isLoggedIn = false client.js:2:1742381
Connected to wss://climatejustice.community/api/v3/ws client.js:2:934379

This is what happens if I try to setup the site:

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). moz-extension:33:9
httpbase: https://climatejustice.community client.js:2:930676
wsUri: wss://climatejustice.community/api/v3/ws client.js:2:930705
isHttps: true client.js:2:930731
No JWT cookie found. client.js:2:933009
isLoggedIn = false client.js:2:1742381
Object { op: “CommunityJoin”, data: {…} }
client.js:2:182972
Connected to wss://climatejustice.community/api/v3/ws client.js:2:934379
Object { op: “CommunityJoin”, data: {…} }
client.js:2:1753378
Object { op: “Register”, data: {…} }
client.js:2:182972
Object { op: “Register”, data: {…} }
client.js:2:1753378
jwt cookie set client.js:2:933177
Cookie “jwt” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read SameSite cookies - HTTP | MDN client.js:2:154567
Object { op: “GetSite”, data: {…} }
client.js:2:182972
Object { error: “user_already_exists” }
client.js:2:1753378
DEPRECATION NOTICE: “backgroundColor” is being deprecated. Please use the “style.background” property. client.js:2:535772
Object { op: “CreateSite”, data: {…} }
client.js:2:182972
Object { error: “not_an_admin” }
client.js:2:1753378
DEPRECATION NOTICE: “backgroundColor” is being deprecated. Please use the “style.background” property. client.js:2:535772

1 Like

I think it’s wrong that the initial setup even creates a user if you already have an admin user after installing ynh. So this would be a bug, right?

Can anyone help here?

From looking at your site, that’s likely an app installation bug.
You probably need to file an issue to the yunohost application install script maintainer.

[edit]

Looks like it’s a known bug that needs reopening again.

1 Like