-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Docker issue: "403 Forbidden" #1127
Comments
I suspect that the ping call for the "Check MAA site" is failing, so the server is not coming online.That issue was reported also in the forums at: https://webwork.maa.org/moodle/mod/forum/discuss.php?d=4842 and the solution provided there was to bypass the ping call by creating a local version of The root problem seems to be that no one added the package A long term fix would be to edit Once you either bypass the call to
|
Thanks a lot for your answer and comment, which helped me to pin down the problems. I added the For fixing the
I think this should not be a problem with respect to security. |
Adding
The version of
|
This sort of problem should no longer occur.
|
On an Ubuntu 18.04 virtual server, I carefully followed the instructions on https://github.com/openwebwork/webwork2/wiki/Docker-newbie-instructions to setup up Webwork2 via docker.
On the command line, the last message appearing without
docker-compose up
really finishing isapp_1 | Check in with MAA site
I set the IP address of the server as a hostname in the
docker-compose.yml
file.Opening Webwork2 in a browser gives me a "403 Forbidden" page.
What could be additional diagnostics to run in order to pin down the problem?
Being not too familiar with containers, I find accessing the log messages of the container difficult.
The text was updated successfully, but these errors were encountered: