I have had it happen when I tried replying to a couple of threads. I don’t use a VPN either. I may have been drafting a reply and then left the thread. After hibernating & returning and trying to post the draft and/or a fresh post, it gave me the 403 forbidden error. Waiting or restarting the browser didn’t help. The threads weren’t private, but for some reason, it locked me out from those threads.
I got the 403 forbidden error again on another thread. Changing browser, reloading page etc. didn’t help. But eventually, I did stumble upon something. Perhaps it may offer some clues.
When I tried to submit a post which had script tags in one of the code snippets (nested in the pairs of three backticks), a “drafts offline” message appeared at the bottom of the editor and a 403 Forbidden error alert prevented submission of the post. When I edited out the code snippet with the script tags, the message went away and I was able to submit the post.
@codecademy could you please look into this?
The issue still persists. And it seems to be related to code being posted as @mtrtmk suggested. But it is not limited to script tags. It also happens with code that does not contain tags.
is this error still investigated? It makes the forum difficult to use, that some code cannot be posted. I just tried to post a code snippet and got the error. These two lines in the code are responsible:
A “403 Forbidden” error may occur due to various reasons: insufficient permissions, lacking appropriate resource access, or misconfigured security settings. The server’s settings could be wrongly configured, hindering access, while corrupted server files might also trigger this error. Additionally, during a DDoS attack, resource access could be temporarily blocked to safeguard against the attack.
To address a “403 Forbidden” error, consider these steps: Verify your permissions for resource access. Ensure the server’s security settings aren’t obstructing your access. Temporarily disable third-party browser extensions to eliminate potential conflicts. Reboot your device as a simple troubleshooting step. If issues persist, contacting the website administrator might be necessary after exhausting prior measures.