Can I get a fix yet, please? Is this only happening to me? It seems like specific posts I can’t access, even when I had just made it.
Clearing your cache should fix the issue.
Thank you, that seems to have done it.
Stopped happening on the DevForum PWA. Still happening on PC. Yes. I cleared cache and temp files and cookies etc etc.
Hey, this has been happening to me in the past week now.
I have cleared my caches, history, temp files, cookies, other browsers besides Chrome, tried on my desktop, my laptop, my phone, and my tablet, but the problem still persist.
It logs me out everytime I close all the browsers related to the Dev Forums. I have to log back in again everytime I open a new tab to check the forums, even in the same browsing session.
Can anyone help me with this?
When you visit the forums does this show up
or does this
I’ve noticed when visiting directly as devforum.roblox.com and not https://devforum.roblox.com it will log you out.
1 Like
Yes it shows that on all my attempts.
Ah, that seemed to be the issue for me until I updated all of my bookmarks and links to https:// and not just devforum.roblox.com, weird how you get it even on the HTTPS Version.
1 Like
Why doesn’t it force https 
Oohhh, so after you said about updating the bookmark, I tried checking mine and it didn’t have the “https://” at the front, so I added it and tried again and it finally kept me logged in :D!
Thank you! @NicholasDev
Though my bookmark didn’t have https:// on it initially, it still automatically becomes one for me for some reason @kiansjet
1 Like
After you login it redirects to https
Ah I see.
Hey thanks for posting this! This was my problem too.
I need to update my bookmark now to fix this issue.
I hope sometime though they force the “https://” so we no longer have this issue.
Everytime i close tabs on every devforum page, it usually logs me out. Since its automatic and detects what your account is on ROBLOX.com, i doubt you can do something like Save Password, maybe they should add some kind of button to keep you logged on.
If you add it to your HTTPS Everywhere rules, it should fix the problem.