You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are new credentials to connect to CERNBox. I've put them into dev/cernbox.env in the env repository.
I wanted to first test it in learn-dev.test instance. The instance was redeployed. The Moodle-CERNBox integration plugin does not work (message "This request is not valid. Please contact the administrator if this error persists." from CERNBox), but the config is probably broken on the Moodle side:
@michzimny The automatic configuration script keys on CERNBOX_URL to update settings, and this seems to have a new value in dev/cernbox.env, so it will create new instances whenever configure.sh is run. Can you try again, please? The current settings on learn-dev have the old CERNBOX_URL but the new credentials. It doesn't work for me, but I'm not sure if it's cached something somewhere for me. If the owncloud plugin baseurl really does need to be different from now on, we'll have to update it manually for the other instances.
I'm not sure what could I try, but that's correct that I've changed CERNBOX_URL. In a moment, I'll send an email to all stakeholders to verify it it's really needed.
There are new credentials to connect to CERNBox. I've put them into dev/cernbox.env in the env repository.
I wanted to first test it in learn-dev.test instance. The instance was redeployed. The Moodle-CERNBox integration plugin does not work (message "This request is not valid. Please contact the administrator if this error persists." from CERNBox), but the config is probably broken on the Moodle side:
Is it expected?
When Moodle-CERNBox integration works fine, then the same cernbox config should be copied to the pedagogy instance (pedagogy/cernbox.env).
The text was updated successfully, but these errors were encountered: