Listmonk: I can't reset my own password???

[svtx]

There is no working solution to this problem on this forum, which is why I've asked.

[svtx]

I've used n8n to access the listmonk API using the API user. At least this way I could actually get a hold of my subscribers list. I'll leave it at that as I won't be using listmonk (or Cloudron for that matter) again anytime soon.

[robi]

It's also in the app documentation. There's a post here from June that goes over all the details too.

Not hard to find.

[svtx]

"The provided environment variables from the docs aren't doing anything for me."

Why do you bother replying if you're neither motivated enough to read my post properly nor willing to actually help?

[robi]

And you restarted the app after any changes?

[svtx]

But of course I did, always restarted the app and every time absolutely nothing happens.

I tried every possible combination of no quotes, single and double quotes too.
Admin username, my username, completely new user name. None of it works.

[robi]

It's single quotes from the example and other threads on this topic.

[svtx]

Actually, on the docs page there are no quotes.
The forum mentions single quotes to be the proper way and...
The file itself already uses double quotes.

But as I've said already, NONE of them work at all.

[svtx]

The app's docs page:

[svtx]

The actual file:

[robi]

the export lines run in bash, so if there are special chars in the pw it will fail without quotes.

is the app up to date?
is the username all lower case?
areyou using bitwarden?

[svtx]

Yes, I know that but I'm sure you can see how the documentation is wrong, the forum mentions another thing and when presented with the actual file, yet another case emerges.

At any rate, I really tried ALL combinations here just to be sure. I even tried simple passwords without special characters to see if they break the line but that doesn't seem to be the case either.

Cloudron up to date: YES
App up to date: YES
Username lowercase: YES
Bitwarden: NO

[robi]

I don't see it as wrong, but it could be improved.

The only other thing I can suggest is to try it on the my.demo.cloudron.io server and see if it has the same behavior.

[svtx]

Yes, the behaviour is exactly the same on there.

Steps to recreate:

Install app, leave user management to the app
Login to default admin account
Change admin username and pass (login works, tested)
Add credentials on the env.sh file
Restart the app
No users are being changed or added at all.

However here I'm noticing the following notice in the listmonk settings page now (because here I can actually login, as opposed to my actual site:

"Remove the admin_username and admin_password fields from the TOML configuration file or environment variables. If you are using APIs, create and use new API credentials before removing them. Visit Admin -> Settings -> Users dashboard. Learn more."

Removing the credentials from the env.sh file does not remove this notice btw. (seems to refer to a different config)

[robi]

Maybe the new package needs an adjustment to not step on the external env.sh

@nebulon ?

[nebulon]

@svtx was trying to reproduce this and indeed it seems the environment variables are not picked up anymore for actual login, however if they are set a warning is shown for the admin login.

It seems listmonk does not support password reset as such via the login form!

Looks like one has to fallback to running database queries directly: https://github.com/knadh/listmonk/discussions/2155

I will remove those env variables from the docs, but I am not sure we should add raw SQL queries there in our docs, as they might get stale as well and cause maybe more harm.

[svtx]

I'll just reinstall the app and allow Cloudron users this time. That should prevent the issue from even happening again. No idea why my password stopped working all of a sudden btw, I have'em saved in KeePass...

There should be a note added to this app that if provisioned without user managemend by Cloudron, there's no sane way to reset one's password. That in itself is incredible. Such a good app, such a dumb decision.

Anyway thanks for chipping in and confirming it was indeed not working right. I was starting to bang my head against the wall here.

[nebulon]

@svtx if you want maybe you can raise a feature request in the upstream github repo, maybe they will add it once more users raise this on their end.