As a dev, this type of thing could easily happen by mistake. But they don’t deserve the benefit of the doubt.
The text of the document isn’t where changes likely took place (if we assume this was a bug). The webpage is an annotated version of the constitution with links between headers and “essay” pages containing explanations, references, interpretations, and context. The webpage has dynamic and styled components. It’s possible to break these things in any number of ways. But like I said, no reason to be charitable. If they want us to believe it was a mistake they can prove it.
Just as an example, one thing that could happen is the “essay page” for part(s) of Sections 9 and 10 could have been modified, with the new version having a different URL, and the static page generator was still pointing at the old URL which is no longer valid, which caused the whole section to be invalid, which caused them to be omitted (instead of failing noisily, due to developer incompetence).
I’ve been using a reverse proxy on a Hetzner VPS pointing at my home plex server for years without issue. Maybe this only applies to people running the actual Plex software on a Hetzner VPS?