Forums » Bugs & Problems » Read Message

Looks like the new Update might have broken the Link Restrictions. You get the following when clicking on the stop sign -

Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

This is sort of a major one.

I'm not having that issue. Might've just been a glitch?

I have this on and off, it seems to fix itself after a while.

Yeah, it has self fixed apparently. The weird thing is that the rest of the link options were working, just not that one.

Blaming my update. How could you Berka?

The server itself seems to have been rather unstable the last few days. I hear sharks in the ocean are eating our internet, so I'm gonna say thats the reason.

I should never have doubted you. Damn robonet sharks!

So that's why I can't get my hotspot to work.

So right now I am getting the Error 500 again. I think it happens on all pages for me at the moment

And now it's fine. I'm guessing there are just server glitches while it's doing something or other that clear up quickly. Hopefully they won't persist, but it's not something caused by an update or anything we control.

Last time it got really annoying was when it would take the entire site down for a minute or two several times a day, but Alex upgrading the servers fixed that.

I still have the problem.

Just noting that was supposed to be a 'last time {the server issue} was annoying', I did not mean to state that the server had to be personally upgraded by Alex because you were annoying. There would've been much easier fixes if that were the case obviously.

In my experience 500 is a script crashing. I managed to do something like that on a different site by a memory issue in php (took me ages to find)

It's back.

And fixed.

Here is an update on this: This bug seems to occur whenever a page window was open for a long time (hours) before the link permissions are set. Clinking the link permissions button after this time causes the link permission error to appear. (Is this caused by a formkey expiring?)