Kindly check with Basis Consultant for the same.
And what you have is a server administration problem.
500 error means something went wrong - it could be caused by an infinite number of things, and yes, some of those things may be things you've done, depending on how much permission to shoot yourself in the foot your sysadmin has given you.
You can even (if you try) 500 error by entering bad code into a node. (or, as you hint, a block)
Now, the message you are seeing is generic. Intentionally. But there is much more detailed info about what really went wrong in your logs.
This is deliberate, as many of the error messages may contain sensitive information, including filepaths, and passwords, that common users have no business seeing. Plus one of the most common cause of a 500 error is a deliberate hack attempt, where someone is attempting to exploit the system by providing unexpected input. The last thing you want to do is tell them exactly what they got wrong 🙂
I'm not saying that your 500s were anything to do with a hack ... just that that's a common scenario, and why your error message is obtuse.
Now, there are (at least) three levels of authority on your setup by the sounds.
The thing is, the server admin has to grant you the ability to view your own error logs. This is a pretty basic and reasonable request. And it's the only thing that will tell you what went wrong from your current state of confusion.
Even then, the answer/fix may take some debugging, but you can't progress without either logs or the ability to replicate the situation.
However the troubleshooting steps were all quite sensible, and certainly a good start.
Could have been a combination of bad code in a block (which can be fatal) and caching refreshing eventually after you removed it. That's a pure speculation tho.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.