Skip to content

400 Bad Request Error when reconfiguring existing areas after updating to v4.0.0 #360

Closed Answered by jseidl
mihsu81 asked this question in Q&A
Discussion options

You must be logged in to vote

Hi! Yes sorry about the misunderstanding. Every major release (when the first digit of the version goes up) is potentially breaking.

I've mentioned on the end of the release notes:

If anything looks broken, try first deleting and re-creating the Magic Area. If it is still broken, cut me an issue or come chat on Discord!

Although I've tested a lot during the beta, there are a few odd cases where you might have to delete and re-create some entries. The logs aren't helping much so I wasn't able to pin down what it is but since the config schema changed it might be that.

Replies: 2 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@mihsu81
Comment options

Comment options

You must be logged in to vote
3 replies
@d4g
Comment options

@jseidl
Comment options

@mihsu81
Comment options

Answer selected by mihsu81
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants