Hi, roughly 16h ago there was a bug in Roblox Studio where places owned by groups could not be published, even if the publisher has the highest publishing permissions.
The bug has been fixed, the icons of the places are no longer grayed out, and the “Can’t publish place” warning is gone.
However, at least for me, ever since the bug has been fixed publishing/updating now results in an error. This time, it is printed in the output.
Similar issue
Universe / Game Id: 9938886451
Update: I tried reinstalling Roblox Studio, deleted all the local files too. The problem still persists.
Bumping this because it’s a really major issue.
My game cannot run properly without DataStores, so working on it as a rbxl file is extremely limited for me.
Update: By some stroke of luck, I managed to publish my game without getting an internal server error only once today.
Any new attempts to update it result in the same internal server error message.
Update: I found a small workaround for this bug.
To anyone else who happens to have this issue, instead of using the option “Publish to Roblox as” (which did happen to work successfully for me only once since the bug’s inception), use the option right above “Save to Roblox as”. It seems to always successfully publish/update the place without resulting in an error, but only once per session.
Bumping this once again. It’s been a week now since the issue first started happening.
Well, it’s been two weeks since the issue first appeared and to this day it still prints “Internal server error.” everytime I try to publish my game.
Could a staff member please take a look at this issue? It’s extremely annoying.
Hey @TheOrder_r, just wanted to check in and see if you’re still experiencing this issue?
Hi, I realized what the issue was, the group that hosted the place was owned by an account that doesn’t have full publishing permissions so I moved the place to a different group that I own myself.
I guess the only bug was the fact that the message only stated “Internal server error.” instead of properly explaining why the publishing failed (group owner not having publishing permissions); I wasn’t caught up with the new publishing rules introduced a few months ago.
