Hello,
I am currently setting up WeBWorK for my university on their server. I am currently at the part where I am testing the configuration, and it tells me I should see the WeBWorK home page, but I sadly only see the Apache2 Ubuntu default page. Does anyone have any advice of where I should look into or have run into this issue when setting it up? Let me know.
Have you checked everything mentioned in
https://webwork.maa.org/wiki/Installation_Manual_for_2.18_on_Ubuntu#If_Something_is_Wrong
Did anything look strange? Is the webwork2 app running? E.g.
sudo systemctl status webwork2
Hi,
I assumed you were installing 2.18. Actually 2.19 will be released very shortly and I would recommend installing 2.18 if not 2.19. 2.18 is quite different under the hood than 2.17 but very similar from the user viewpoint. That being said, you should look at https://webwork.maa.org/wiki/Installation_Manual_for_2.17_on_Ubuntu#Test_your_configuration
Especially look at the Apache error log. You say your only see the Apache landing page. Stupid question, but you are trying http://yourserver.yourschool.edu/webwork2, correct?
Also are you installing everything yourself or using the virtual machine image?
Arnie
I must second Arnold's statement. Quite frankly you are wasting your time learning how to install WeBWorK 2.17 (or any version before that). WeBWorK 2.17 relies on modperl2 which is practically obsolete. So eventually, you will need to upgrade and then you will have to learn how to work with 2.18 and beyond, and as Arnold stated, from the administrative standpoint it is completely different since it uses the modern Perl library Mojolicious instead of modperl2. In addition, there are many new features and improvements to WeBWorK 2.18 (and more in 2.19) that you (and your users) will be missing out on. Eventually (actually already for some problems), you will also run into problems with PG 2.17, because the OPL is being updated to work with new things in PG that were not in previous versions of PG.
I would definitely try 2.18 and would recommend starting from a fresh installation of the server. If it's a vm, that is pretty easy. If you just followed the standard installation instructions for 2.17 and downloaded WeBWorK from git hub, then you would have actually downloaded 2.18 and then followed the 2.17 instructions which would explain why things didn't work.
Arnie