I just tried a curl -I to your site for both http:// and https:// ... the https:// didn't respond at all, so you probably do NOT have a re-write rule to force ANY/ALL traffic to your site to one or the other ... that was another possible for seeing this 'behavior'.
Ok, if you think that adding that line to config.php is the issue, comment it out using // in front of that line. The only reason I suggested was knowing some sites may have set use https for login only and you hadn't mentioned that. In the actual mdl_config table for that variable set to use https on login the value is a '1' (ON). In the actual mdl_config table for that variable set NOT to use https on login the value is '0' (OFF). I checked the tables of two sites. I do NOT know if Moodle will see '0' the same as 'FALSE' or not.
So do we know what the errant sed command did replace?
Here's my latest contribution ...
Docs at:
https://docs.moodle.org/28/en/Moodle_migration
show this:
sed -e 's/oldserver.com/newserver.com/g' oldmysqldump.sql > newmysqldump.sql
which is proper of moving a server from old domain name to new domain.
What you were attempting to do is not only move to another domain but also change
the 'protocol' ... from https:// to http:// thus, got caught in a 'catch 22' due to
usage of sed.
Your posting said this command didn't take:
sed -e 's/https:/oldserver/http/newserver.com/g' oldmysqldump.sql > newmysqldump.sql
So your sed command found stuff but incorrectly.
In your line above: https:/ is missing the second '/'.
Yours: https:/oldserver
should have been
https://oldserver ... note the //.
One of the things I don't like about using 'sed' is the delimiter between the search term and the replace value .... which, according to the docs is a '/'.
But, IF one had the original site at: http://sites/moodle/
one would want to search for http://oldsite/moodle/ and replace with https://newsite/moodle/
note the slashes and the trailing slash in the search/replace might confuse sed as a '/' character is the delimiter between the search text string and the replace with text string.
According to sed manual:
`/REGEXP/'
This will select any line which matches the regular expression
REGEXP. If REGEXP itself includes any `/' characters, each must
be escaped by a backslash (`\').
Translation:
Sed uses regexp which in itself is somewhat difficult for 'rookies' to use.
(PS, I'll include myself in that category).
Another poster has already spotted the error and relayed the correction.
So your sed command should have used \ in front of every / ... which means the suggested use of sed had to be modified for what you wanted to do ... replace https:// with http://
should have looked like:
https:\/\/oldsite\/
and replaced with
http:\/\/newsite\/
That's why I like nano editor ... no need to 'escape' anything like '/''s.
Now that you've run through sed incorrectly, what do we have in the .sql file?
The same https.
You can reach your site ok with http intiially cause Apache can handle the mis-information contained in the DB but any click to login (even if going directory to the form to login) will result in Moodle attempting to use https:// which isn't configured in your apache at all. Thus fail.
So, using nano, load up a fresh sql dump of the DB.
After it comes up, do [ctrl][w] for a search of the sql file.
Search for parameter: https:// [ENTER]
Check to see what it finds ... is it finding the URL to your site?
Check for the next instance: [ctrl][w] again - [ENTER]
Did it find the next instance correctly?
If those check out, then do a find and replace.
[CTRL][W]
[CTRL][R]
First dialog box ask for what to find to replace.
and search for 'https://yoursite/'
Why not just https? You probably have 100's if not 1000's of resource links.
And you want to replace ONLY the links that point back to your own Moodle.
Then replace with 'http://yoursite/'
Rather than doing every instance in single fashion, once you are sure it's finding and replacing correctly, use the 'All' switch for the remaining items to replace.
That might be slow and appears to hang ... give it time. Be patient.
When it finishes, SAVE the .sql file:
[CTRL[[X] you will be prompted to save the changed file.
Keep same file name.
Once that's done, then do the import of that edited sql file into a
**new** database for the moodle.
Change config.php file for the new DB name.
Now try your site.
Also a word of caution about these directions ... I've tried to provide specific
directions but am doing so from memory - at 67 now I find that sometimes the synapses/links have
gone a-stray. ;)
'spirit of sharing', Ken
