Posts made by Visvanath Ratnaweera

Picture of Particularly helpful Moodlers Picture of Translators
The question is whether this is a Moodle problem or a Fortigate problem. As far as Moodle is concerned, if your Moodle site will be https://example.com, then that is what you put in $CFG->wwwroot. Worth testing that short-circuiting Fortigate. Especially since Moodle server and the browser both don't like a back-and-forth between HTTP and HTTPS. They cache these things and get confused.
 
And the "mixed" error is a tell-tale sign. Every time you change $CFG->wwwroot you need to Search and replace the URL in the database.

Once you're certain that Moodle works as expected then you can bring Fortigate in to the picture. Unlikely that there are many here who knows the product. This is the first time I saw it.
Picture of Particularly helpful Moodlers Picture of Translators

I'm deeply sorry. Dragging AI in to this misfired. 

>>> This is insanity. I am definitely out unless somebody of King Solomon's caliber (AI?) visits us.

It was supposed to (literally) say that I am out unless a higher authority like King Solomon or in his absence the omnipresent AI would come to the rescue. Which was pun. The meaning behind it was, since both events are unlikely, I'm out. Now I see, an or  as in (or AI?) could have helped.

Either way, I never doubted Carl could be an AI agent.

Signing out..

Picture of Particularly helpful Moodlers Picture of Translators
This is the most bizarre discussion I ever had on moodle.org. @Rick, you said most of my six assumptions are true. @Ken, you say OP has only a database dump. Is it the point where you left the discussion? Why didn't you tell the others? Reminded me a guy who planned to put a car together after finding four discarded wheels!

This is insanity. I am definitely out unless somebody of King Solomon's caliber (AI?) visits us.
Picture of Particularly helpful Moodlers Picture of Translators
Hi

You wrote:
> Started with 4.4.2, upgraded to 4.4.4 (the latest), with no issue, everything runs smoothly,

Yeah, one needs to keep abreast in the Moodle version, 4.4 in your case, if nothing else to close known security holes.

> Then decide to upgrade to 4.5, which start having issue.

The purpose/need? I mean, what is that you need in 4.5 which 4.4 does not have?

> After extract the 4.5 to the folder and open the site for install/upgrade process,

Sounds dangerously like you overwrote the directory, not replaces it. You are following Upgrading Moodle, I assume.

> browser shows error 500 then error 503.

That is an error thrown by the web server (not Moodle) when something major has gone wrong. Typically file permissions but also stale caches can play havoc.

> Unable to proceed to any pages, and can only revert back to 4.4 (Latest) by replace all the files.

Who told you that? Could you provide your source?