Closed paulo-roger closed 2 weeks ago
Works for me with Safari and MacOS. And I'm not seeing that Content Security Policy error (could be caused by a browser extension or something?). Maybe have them try clearing site cache/cookies?
I have asked them to clear the cache and the problem persists. Maybe could it be a 2FA error then?
Possibly. Have them try clicking the login link at the top right and login there. Instead of using the form under the search field. It might give a more helpful error message.
On July 31, 2023 4:38:59 PM EDT, paulo-roger @.***> wrote:
I have asked them to clear the cache and the problem persists. Maybe could it be a 2FA error then?
-- Reply to this email directly or view it on GitHub: https://github.com/rystaf/mlmym/issues/63#issuecomment-1659129112 You are receiving this because you commented.
Message ID: @.***>
@rystaf I'm on macOS and can login too, wasn't able to prior to fixing a 2fa issue and updating to lemmy 0.18.4 + mlmym 0.25.
I didn't try again for like 2 weeks after I opened a separate bug report, thinking it was the 2fa (would get 400 or 401 depending on password/2fa combo tried) or extra / in the URL. Today I did turn 2fa on and back off, then decided to give old.instance.com a try and everything works no problem now.
Since getting mlmym working earlier, I just updated it to the latest versions and can confirm I am able to login (without having 2factor enabled at least) on macOS with the following versions installed:
lemmy / lemmy-ui docker: 0.18.4 running rootless and mlmym: 0.0.27 also running rootless, on a separate VM.
When I couldn't log into the my instance with mlmyn I looked at the dev console and it was because I hadn't set up https for mlmyn so it couldn't store any secure cookies.
I hadn't set up https for mlmyn so it couldn't store any secure cookies.
@JakeShirley May I ask how do you set up https for mlmym? I'm a noob regarding docker. I've been able to run the mlmym docker image and it works... until I try to log in, which does not work.
[EDIT: It's definitelly cookie related because I got it working by manually adding the cookies sent on the Response Headers (Set-Cookie)]. Not sure if the problem is HTTPS because I have a Commafeed instance working on HTTP and it seems it has no problem with cookies... but it's worth a try.
Thanks!
This may have been caused by a bug fixed in 0.0.46 that prevented logging in with email address instead of username. If this is still happening to anyone, please let us know with any details you can provide.
I think it is worth investigating.
I have had users from 2 different instances reporting they are not able to login from MacOS.
Here is a video and a Console screenshot: