Then this might be a different problem than the suggested solution in this topic had in mind:
and I’m also wondering if the option name change was intentional. From the server help text:
2.0.9.101
--webservice-allowed-hostnames: The hostnames that are accepted, separated with semicolons. If any of the hostnames are "*", all hostnames are allowed and the hostname checking is disabled.
2.0.9.102
--webservice-allowedhostnames: The hostnames that are accepted, separated with semicolons. If any of the hostnames are "*", all hostnames are allowed and the hostname checking is disabled.
You might need to go back to 2.0.9.101, or wait for the right developer to figure this out further.