Hi Forum
I'm using a Moodle 4.1 release and have just switched over to using HTTPS.
Each time I now try to login I get "Invalid login, please try again"
This is a Bitnami version if that helps . . .
Rgds
Bob
Change the url in config.php file of moodle code root.
Then you must run a conversion tool
https://site/admin/too/httpsreplace/
to replace all the DB records that refer to your site when it was http.to https
Afterwards, good idea to purge all caches.
'SoS', Ken
Is that a new tool? In addition to the basic replace tool? I learn something new every day!!
There's only a little typo:
https://site/admin/too/httpsreplace/ -> https://site/admin/tool/httpsreplace/
It's accredited to "Copyright (c) 2016 Blackboard Inc. (http://www.blackboard.com)" and it seems available almost since Moodle 3.1 ( I didn't know of it ... )
Opps ... 'fat fingered' that url! Sorry 'bout that!
Thanks for correcting!
'SoS', Ken
Not new tool! 
Been present for a while now:
find ./moodle3?/ -name httpsreplace
./moodle34//admin/tool/httpsreplace
./moodle35//admin/tool/httpsreplace
./moodle36//admin/tool/httpsreplace
./moodle37//admin/tool/httpsreplace
./moodle38//admin/tool/httpsreplace
./moodle39//admin/tool/httpsreplace
./moodle34//admin/tool/httpsreplace
./moodle35//admin/tool/httpsreplace
./moodle36//admin/tool/httpsreplace
./moodle37//admin/tool/httpsreplace
./moodle38//admin/tool/httpsreplace
./moodle39//admin/tool/httpsreplace
Present in version 4's as well.
'SoS', Ken
Oh wow...guess I have always just used replace. As I said, always learning new stuff!
Since this is posted in Security/Privacy forum, there is yet a 'better' way.
If one has only Web access to the site, tool is the only way.
If one has command line access to server ... the old way could be best.
site in maintenance mode
use text based editor - nano comes to mind - do search and replace with nano
New database changing the creds to the DB
Import the edited sql dump into new DB
Change config.php file ... dbuser, dbpassword, dbname.
site out of maintenance mode
Done.
Advantages in doing above - security obviously - but as a side affect, new DB has been optimized.
That might be best cause I see scans quite frequently for phpmyadmin vulnerabilities - especially when there has been an upgrade to phpmyadmin.
I don't use phpmyadmin ... and when I see massive scans at it, not at all shy about blackholing that IP address at the network level.
'SoS', Ken
Hi,
Update Moodle Configuration
Clear Browser Cache
Ensure that your SSL certificate is installed correctly?
Check Base URL
Verify .htaccess Configuration
Update Database Records
Check Bitnami Configuration
Verify Server Logs
Contact Bitnami Support
Temporary HTTP Redirect:
Great day start with helping each other
Here i am sharing my experience with HTTPS issues:
If you are experiencing "Invalid login, please try again" issues after switching to HTTPS in Moodle, there are several potential causes for this problem.
Here are some steps you can take to troubleshoot and resolve the issue:
Update Moodle Configuration
Clear Browser Cache
Ensure that your SSL certificate is installed correctly?
Check Base URL
Verify .htaccess Configuration
Update Database Records
Check Bitnami Configuration
Verify Server Logs
Contact Bitnami Support
Temporary HTTP Redirect:
You have to verify these mentioned this details. So you will get the better where you facing the issue.
Note: Always proceed with caution when making modifications, and if you have any questions, feel free to contact Bitnami support, your hosting company, or the server administrator. Moreover, it's always a good idea to make backups before making big changes.