-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public Policy page down? #225
Comments
The hosting server datacentre has a "small" fire issue, and we are preparing a new machine (nothing lost, but need some time for installing everything and retrieving from backups). |
I'd like to add to this Issue, as I've tried to upload a new public policy through the web UI, and MediaConch GUI but have receiving error messages repeatedly. This was the start of March. I've been logging in as username BFI-DDP. Happy to run some more tests if you need more details. |
Thanks Jerome for confirming, hope it isn't too much work for you all! |
@digitensions it is not the same issue, yours was an issue with a new version of a web library which was blocking (for security reasons... too much security here) the upload, @GuillaumeRoques fixed it and just after that the server was transformed in smoke, so your issue is fixed and all should be OK when the new server is installed. Note: the good thing here is that this service availability issue shows us that the public policies are used :-p. |
Thank you Jérôme, that's fabulous! Much appreciated. We're really excited to offer a public policy, it's such a great service thank you! |
The new server with MediaConchOnline and the public policies is up, everything should work as expected! |
Hello all,
I am trying to take a look at the public policies available, and am getting the following message when I try to access it through the GUI (the link at [https://mediaarea.net/MediaConchOnline/policyEditor] is also not loading for me).
I just wanted to check is this to be expected at the moment?
I have attached a screenshot, and am using version 18.03.02.
The text was updated successfully, but these errors were encountered: