403 "Forbidden" errors on edits

Update: problem solved. It was a bug that very few would have seen.

For over a month now, I’ve been attempting to fix a typo (actually a thinko) on my “Hosting your own git repositories” article, but Substack hasn’t fixed this problem, and I’ve tried messaging them and tweeting them to no avail. I’ve tried using both Firefox and Chromium on Debian 10.8, as well as on mobile Safari on an iPhone 8, all with the same error. The page itself alerts that there’s a “Network error”, but the Javascript console shows it’s actually 403 “Forbidden” errors on the PUT request sent by the browser. Obviously a server-side issue. I can’t believe I’m the only one having this problem, or that their IT team hasn’t seen the problem surface while analyzing server logs. Splunk, or whatever is used nowadays; I’ve been out of the industry for over 2 decades now.

Anyway, I have little hope of reaching them this way either. But at least I’m not seeing the error on this new post, only on editing older ones.

[Update: the problem has been resolved. It turned out to be due to typing “/еtc/hosts” (which I assume substack is blocking out of fear of its own server being hacked?!), for which I found a workaround of pasting in the Cyrillic “ye” character, which looks the same as Latin “e”). So this bug would only have been seen on posts that referenced that particular file.]