I'm getting a 403 (Forbidden) error when trying to update homebrew monsters today. I tried clearing cache and cookies as well as a newly-installed browser, still getting the same error. Has anyone else seen this recently?
Tried on different browsers and that didn't help. I can create new homebrew items from scratch but when i try to edit this one specific background that i had previously created, every time i get the 403 error.
I appreciate the help. Since I seem to be able to create new backgrounds, I'm just gonna delete it and start over since I am NOT super tech savy. Thank you so much for your time, though
There was no popup. It was a generic Chrome 403 page with nothing but "403 Forbidden"
While trying for a 5th time to capture network traffic request data, it began working.
I had just published a change to another homebrew item, so I hypothesized that there could be some throttling mechanism to avoid AI slop bots spamming homebrew, but after publishing another item, I was able to update and publish other homebrew items with no issue
To be clear, I'm no longer stuck, but I did run into the same problem and wanted to provide this data point and witness account in the hopes that it can help others and/or help to track down this long-running problem.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm getting a 403 (Forbidden) error when trying to update homebrew monsters today. I tried clearing cache and cookies as well as a newly-installed browser, still getting the same error. Has anyone else seen this recently?
I'm also running into this issue.
-
View User Profile
-
View Posts
-
Send Message
ModeratorCan you try on a different device and network too to help isolate things?
// I am Arenlor
Developers should read This Changelog
Moderator for D&D Beyond's YouTube, Twitch, and Discord.
I am getting this as well when I try to update a homebrew background
-
View User Profile
-
View Posts
-
Send Message
ModeratorThe troubleshooting steps are required to provide a solution.
// I am Arenlor
Developers should read This Changelog
Moderator for D&D Beyond's YouTube, Twitch, and Discord.
Tried on different browsers and that didn't help. I can create new homebrew items from scratch but when i try to edit this one specific background that i had previously created, every time i get the 403 error.
-
View User Profile
-
View Posts
-
Send Message
ModeratorCan you try clearing the cache and cookies and seeing if it behaves then?
// I am Arenlor
Developers should read This Changelog
Moderator for D&D Beyond's YouTube, Twitch, and Discord.
I did. Still not behaving. LOL
-
View User Profile
-
View Posts
-
Send Message
ModeratorThere should be a block that pops up with information including the time and page URL, can you copy and paste it for me?
// I am Arenlor
Developers should read This Changelog
Moderator for D&D Beyond's YouTube, Twitch, and Discord.
https://www.dndbeyond.com/homebrew/creations/create-background/365139-charlatan-5e/edit
-
View User Profile
-
View Posts
-
Send Message
ModeratorI need the time and all too.
// I am Arenlor
Developers should read This Changelog
Moderator for D&D Beyond's YouTube, Twitch, and Discord.
I appreciate the help. Since I seem to be able to create new backgrounds, I'm just gonna delete it and start over since I am NOT super tech savy. Thank you so much for your time, though
They did nothing to fix this.
I got this error as well.
URL: https://www.dndbeyond.com/homebrew/creations/magic-items/11227511-arrow-of-get-over-here/edit
Time: 2026-02-16 @ 1830 MST
There was no popup. It was a generic Chrome 403 page with nothing but "403 Forbidden"
While trying for a 5th time to capture network traffic request data, it began working.
I had just published a change to another homebrew item, so I hypothesized that there could be some throttling mechanism to avoid AI slop bots spamming homebrew, but after publishing another item, I was able to update and publish other homebrew items with no issue
To be clear, I'm no longer stuck, but I did run into the same problem and wanted to provide this data point and witness account in the hopes that it can help others and/or help to track down this long-running problem.