Are you sure you're logging into https://pawb.social and not http://pawb.social? (difference is the s)
this post was submitted on 14 Aug 2024
9 points (84.6% liked)
Pawb.Social General Lounge
171 readers
3 users here now
An all-purposes general community for Lemmy / Mastodon related discussions that affect (or inform) all of our community.
Rules
- Pawb.Social Code of Conduct applies
- Posts must be Lemmy / Mastodon related, or related to the operation of our communities
founded 1 year ago
MODERATORS
I don't understand why the http doesn't redirect to the https
Yep!
So I guess the follow on, is how are you browsing? desktop, phone, app? What browser? What extensions? What cookie settings?
headdesk Thought I'd fixed it by clearing the "site data and cookies" for this site v.v
I'm using Firefox 129.0.1 on Arch Linux (bytheway ๐ ), Enhanced Tracking Protection is on Standard. I do have a bunch of add-ons, but the only one I've changed recently was trying out ยตBlock Origin Lite in place of ยตBlock Origin (disabling the latter to try the former). I've since reversed that, to no visible effect. I've also got...
- LocalCDN, tried switching that off for this site. No luck.
- NoScript, with everything here set to trusted.
- Privacy Badger, which sees no trackers here
- A pile of other random stuff like Dark Reader, FoxyGestures, and Indie Wiki Buddy. Violentmonkey, I suppose. Shows no scripts for this site, though. Twitch Chat Pronouns. FFZ. Instance Assistant for Lemmy and Kbin? Maybe that's janked something up. ..... Nope!
Looks like it's only new tabs doing the thing now. I could've sworn it was any new page, but right now it seems I'm fine as long as I don't open a new tab. Also I did update Firefox possibly around the time this started soooo... maybe I'll blame Mozilla. Also maybe I'll finally start switching to another browser. ... Based on the same one anyway. Bleh.
[Lie/Joke] Or maybe good old Google Chrome will be my home ๐คฃ
hmmm. I will assume you've restarted the browser completely at some point.
If you open up web developer tools (ctrl+shift+i) when you load pawb.social, with each request, in the cookies tab, or in the request header you should see one cookie jwt: "xxxxx". DO NOT SHARE THIS TOKEN. Its a pretty simple system. You might have some containerizing of tabs going on which will not allow the cookie to share across tabs. It should show if anything is being blocked, or your just not sending the cookie with your request.
The other items in my request header for the root of pawb.social are
Accept : "image/avif,image/webp,/"
Accept-Encoding : gzip, deflate, br
Accept-Language : en-US,en;q=0.5"
Connection : keep-alive
Cookie : jwt=hahahaha
DNT : 1
Host : pawb.social
Sec-Fetch-Dest : document
Sec-Fetch-Mode : navigate
Sec-Fetch-Site : none
User-Agent : Your user agent
Looks like it's there even in a new tab. Logging in again gets me a new one, which works... until I open another tab. Interesting thing, I can duplicate a tab and that one shows me logged in. Hmmmmmm. ๐ค
Okay, had some more fun. I've got a heisenbug ๐ Sometimes opening a new tab works as expected, sometimes it doesn't. Duplicating a tab seems reliable, but that's kindof a goofy way to browse.
GET / HTTP/1.1
Host: pawb.social
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/png,image/svg+xml,/;q=0.8
Accept-Language: en-GB,en;q=0.5
Accept-Encoding: gzip, deflate, br, zstd
DNT: 1
Sec-GPC: 1
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: cross-site
Connection: keep-alive
Cookie: jwt=hunter2
If you didn't see the edit, @[email protected] seems to have determined its an issue with NoScript https://pawb.social/comment/10303654
Lemmy on desktop is pretty much all javascript, so that doesn't surprise me too much. It still sounds like some containerizing is going on. and a logged out header would be more interesting. If that was a logged out header, that's really strange because I wouldn't expect to see the cookie with the request.
Thanks, but that's the first thing I tried after seeing that post :-\ Didn't work for me. Muchly weird. Problem seems... less bad now? Sometimes pages load logged-in, sometimes refreshing helps.
Also, nowhere else seems to have this issue. Maybe the server hates me personally v.v
It sounds like its time to create a new profile and start adding your addons one by one until you see the weird behavior. When it breaks try disabling or removing the breaking one on your original profile. I can't think of anything else to try. Good luck. about:profiles
I have pretty much the exact same setup as you and started noticing this same issue right around when I installed NoScript (even though everything was set to allow). Let me do some testing and I'll get back to you.
UPDATE: after completely disabling the extension, the issue seems to have gone away. Not sure what's causing this (and tbh I don't really care enough to dig around and find out)
seem to be fine for me. Though I was logged out when I visited Lemmy just now, which is unusual :3c
I suspect there was something going on and it's fixed now.
Edit: I was also logged out the next day, maybe some kind of new session invalidation or cookie expiration :3c
๐ This isn't just you! We're aware of the issue and believe that the latest version of Lemmy should fix it; It seems to be an issue with the cookies being set with Strict instead of Lax causing it to not be sent by your browser.
Full announcement for maintenance to perform the upgrade: https://pawb.social/post/14286683
I haven't had any issues staying logged in on the same tab, but I have to log in again every time I open anything on this instance on another tab.
That sounds like my issue. I solved it by switching to Floorp ๐
I'm guessing Firefox very recently got an update that broke something and it's not in Floorp yet ๐คท That or I just accumulated jank in that profile over the years and that broke something. Idunno.
Well, that's the thing... I probably should have mentioned this in my first post but I'm using Vivaldi, which is a Chromium fork. So it's not just a Firefox issue.