Hi
You wrote:
> everything was working fine until I upgrade this to 4.4.3
You upgraded the httpss://foo.com/moodle310 following
Upgrading and newer version too worked as httpss://foo.com/moodle310, right?
Note: The name Softaculous rings alarms. It has a reputation of violent upgrades, i.e. forcing upgrades even when Moodle says No!
Talking of violent upgrades, you know that you can't jump Moodle 3.10 to 4.3 in one step - unless
https://foo.bar/moodle310 was not Moodle 3.10? Ref.
http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases> and enable MFA plugin.
That is an entirely different step. Which MFA plug-in specifically? Why is it connected to networking? The
hosting provider imposed an IP rule without asking you? ..exactly when you added MFA?
Yeah, it must be a network issue, if those things can happen. But networking is not the
domain of these forums. Moodle is a web application which runs on the OS, which in turn sits on the network. So doesn't communicate with the network directly. But the network comes before the application. It can play havoc with Moodle. You have to settle them before coming to Moodle.
Ken has an idea. You may want to follow him. Otherwise, you have to start from the basics: Make all the network jugglery vanish and make the
server react to the public IP address, say
https://x.x.x.x/moodle310/test.html - once you created a test.html file in the moodle/ directory. Notice that the above web page doesn't go through Moodle. Same with a ../phpinfo.php file. Then switch to
https://foo.com/moodle310/test.html, phpinfo.php.Then move on to Moodle, ../index.php which is Moodle.