For the past week roblox studio has logged me out and forced my to login everytime i open it, constant ‘internet’ issues when my internet is fine with literally everything else even playing games on roblox. It constantly forces me to login to every window when i try and test and thats if it allowed me to sign into the first time to open studio.
constant error issue that pops up 75% of the time as well as the login with browser tab
opening studio, any studio place and testing with ‘local server players’
Expected behavior
I expect roblox to not throw me an internet error when my internet is working just fine, I expect it not to log me out of studio every single time i reopen or test. Shouldn’t be having these issues at all.
I’ve cleared my cache data in browser, uninstalled all of roblox and deleted appdata files then re-installed twice, I’ve reset my wifi a few times, and Updated my drives and pc as well.
Can you please find the corresponding log from those failed session and DM me please?
We can take a look to see what is going on. The two dialog you screenshot means some initialization steps failed during startup actually. (sorry about the confusing text…)
I’ve been having so many issues in the last 5 days or so. Studio will freeze on start when it shows the logo. Then, other times, it gets stuck saying logging in forever. When I do get it open, it then wants me to login every time. Logging in via Studio does not ever work, I can only login via the browser. Sometimes that doesn’t work. The, when I load into a project, it will occasionally not properly load everything, sometimes with missing textures or meshes, including ones from native Roblox files like material textures. Half the time test mode fails to load many things. Coming out of test mode will freeze Studio a third of the time.
I’ve never had these issues before. I haven’t changed any plugins, not that that would cause most of this. I’ve even had this new UI long before, and it worked fine. Just something in the last 5 days or so has completely destabilized Studio for me.
Same here, I was getting logged out multiple times as well but was able to log back in via browser. Output gets spammed with 403 errors non stop though despite being logged in. Been happening for about 5 days, tried reinstalling and it didn’t help
Multiple posts have been created regarding this issue, yet no action has been taken. Its affecting my development process. Just like everyone else, it started a few days ago.
I am having the exact same issues and it’s really detrimental to our team’s workflow. I’ve noticed that these issues only happen when my DNS server is routing apis.roblox.com (and maybe other roblox requests) to the server in VA (iad4), and especially yesterday it was very bad, I could not login at all. Today it is intermittent. I was using Quad9 dns (9.9.9.9) which always seems to route me to the iad4 server, and cloudflare (1.1.1.1) sends me there occasionally. For me a temporary workaround is to use Google DNS (8.8.8.8) which seems to route me to NYC servers which works fine.
I thought I was going crazy when this started for me about a week ago from posting this. But I’ve been getting these connection issues both on studio and on the player client at times. On studio especially, every so often it also just closes on its own while I’m in the middle of working.
I’ve been having the same issues for the past week as well! I’ve noticed this only happens when connected to Roblox on my home internet IP. Located in mid-Atlantic region too and these issues only arise when connected from this region (not when using my mobile hotspot).
This has also been happening to me too, it takes like 5+ attempts to get in, and then there’s still a big chance for it to get stuck/load for a long time when loading up a place. What’s also weird is that it feels like its only happening to me compared to some others.
I’ve probably crashed / had to reopen Studio at least 25+ times now in the past week due to these issues. Very much awaiting a fix, as this is a frustrating issue causing me a lot of time.
The backend team didn’t find anything specific from their investigation. At the moment we also cannot reproduce the issue. So we will close this ticket internally for the moment.
If you run into issues with a solid repro, feel free to resubmit issues and please DM log if possible.
