> I used this link to provide the info in my original post.
Apologies. I try to make sure every post gets answered - but I don't always have time to read them fully....
> The rest of Webtrees is working normally.
Does this include the other tables that load data dynamically. e.g. website logs or tree-changes logs?
>> If your server uses Microsoft IIS
> I don't know. Is there a test or query I can run to find out?
The HTTP headers may tell you.
The "Server information" section of the control panel may tell you.
But if this is not your server, then you won't be able to change the config, so knowing this won't really help...
Your server is blocking the URL.
It could be the length. It could security software on the server. The only way to find out might be to ask your web host.
> Does this include the other tables that load data dynamically. e.g. website logs or tree-changes logs?
I could only find three items in the control panel that use long urls:
Manage Media 12 lines of text.
Website logs 22 lines of text.
User Management 34 lines of text.
I don't have a tree-changes log.
User Management is the only one that fails.
I know you are a busy man and doing a great job but could you explain why User Management url is so long.
If its related to number of users I could try deleting some inactive users using phpadmin?
> but could you explain why User Management url is so long
The table is populated dynamically. Each time you change the page length, scroll to a new page, search, etc, a new request is sent to the server. There are a lot of options to send. Which columns to sort by, which columns to filter by, etc.
The request URLs aren't excessively long by any standard. A couple of thousand characters.
> Website logs 22 lines of text.
website logs and user list both use the same dynamic tables, and both have equally long URLs.
If you were hitting the IIS default limit, then both would fail.
So this suggests URL length is not the issue.
What we are left with is a server firewall-type message that has blocked a specific HTTP post request that contain the keyword "user".
It is happening before the request even gets to webtrees.
My guess is some sort of security software on your server is blocking these.
I think the only solution is a support ticket with your host.
They give you an ID number in the error message. They can presumably use this to tell you why the request was blocked.