Quantcast
Channel: Installing and upgrading help
Viewing all 46891 articles
Browse latest View live
↧

Re: Moodle 3.5.5 + 3.6 After successfully installation - Setup Main Admin Account, cannot see password input field

May 14, 2019, 1:43 pm
$
0
0
by Ken Task.  

Congrats!  Very useful info!!!

According to:

https://httpd.apache.org/docs/2.4/mod/core.html#acceptpathinfo

Those remotely hosted, according to above might be able to use .htaccess where acceptpathinfo can be turned on ...

server config, virtual host, directory, .htaccess

While the following is for 1.9, there is an example of .htaccess and acceptpathinfo on

https://docs.moodle.org/19/en/Create_.htaccess_file

If you have Apache version 2 installed, add these lines:
<IfDefine APACHE2>
    AcceptPathInfo on
</IfDefine>
Otherwise add this single line:
AcceptPathInfo on

'spirit of sharing', Ken


↧
Search

Re: Moodle 3.5.5 + 3.6 After successfully installation - Setup Main Admin Account, cannot see password input field

May 14, 2019, 1:57 pm
$
0
0
by Jon Bolton.  

@martin... which is as per the documentation at https://docs.moodle.org/36/en/Nginx which has been there since 2015.

I say that not to score points or be patronising - rather to point out that the Moodle documentation is fairly extensive and robust and well worth a search if you have a problem smile

↧
↧

Re: Moodle 3.5.5 + 3.6 After successfully installation - Setup Main Admin Account, cannot see password input field

May 14, 2019, 2:40 pm
$
0
0
by Martin Williams.  

I viewed that documentation and added the code verbatim and it didn't work. After reading several other posts I made changes to two of the lines in the block to get it to work.

↧

Re: Moodle 3.5.5 + 3.6 After successfully installation - Setup Main Admin Account, cannot see password input field

May 14, 2019, 7:03 pm
$
0
0
by Jon Bolton.  

So then maybe things have changed in the software since the documentation was added - but the documentation is part of the Moodle project and you can contribute your experience by updating it so that others can benefit too smile

↧

Error reading database - solved. BUT WHY???

May 14, 2019, 8:17 pm
$
0
0
by Lisle Waldron.  

Its been five days without sleep. I have a Godaddy VPS that I'm migrating from shared hosting over to. I can install a fresh install with no problems... but my migration (and update) has been nothing but headaches. Followed the Moodle migration information and it worked well save one qwerk that I can't wrap my head around. Even though my database is all converted to Barracuda and my database is utf8mb4_unicode_ci I get an issue trying to log in where I get an error that says, "Error writing to database".

Now I even created a table and tried to connect and insert data via SQL from the PHP page just to test if I could write to the database. It worked fine. All my php bits seemed to be fine otherwise. After much digging I found one line in my config file that makes or breaks my instance. If dbcollation is set to anything other than -  'dbcollation' => 'utf8_general_ci', - it will not work.

The old/original config.php file does not work. Deleting it pushes through the new file creation but it creates the new config.php file with a utf8mb4_unicode_ci collation. The instance will load, I'll enter my login creds, hit login, and get "Error writing to database". 5 days later I rule out too many things and end up stumbling on an old config file that had the dbcollation as utf8_general_ci and it works beautifully.

What gives? Why must I use the utf8_general_ci instead of the utf8mb4_unicode_ci in the config.php file to get this to work? The former shared hosting instance was running 3.4.5 and I upgraded to 3.6.4 as it was available mid-process.

Help?!

↧
↧

Re: Moodle install

May 14, 2019, 10:52 pm
$
0
0
by Alain Jacquet.  

"You need to put all the moodle files into /etc/www
Put them in the root of www if you want or in a folder IE: /etc/www/moodle"

I would like to know what the impact is of having all the Moodle files under the moodle subdirectory. Will the site respond to the url to the home page, or will you need to put in the url followed by the path /moodle:
eg: http://urltosite.com/moodle      or http://urltosite.com

Which one will work?

Thanks

↧

ISP Limitations - MariaDB (Antelope)

May 14, 2019, 10:58 pm
$
0
0
by Alain Jacquet.  

I am trying to get a moodle instance set up on a shared webhost platform. There is a limitation on the way the database can be set up:

1. they use MariaDB (up to date version)

2. The server uses Antelope structure for DB.

The latest versions of Moodle (I tried 3.6.4) all require that the Barracuda file format be used for the Database.


The limitation means that I can't use the latest version of Moodle - but now I'm stuck:

  • Which is the last version that permits you to use the Antelope database structure?

Thanks in advance...............


↧

Re: ISP Limitations - MariaDB (Antelope)

May 14, 2019, 11:36 pm
$
0
0
by Jon Bolton.  

If you're really stuck, you can edit your config.php file and change the dbcollation to this:

dbcollation' => 'utf8_unicode_ci'

Please be aware that this is far from an ideal solution and you may run in to problems in the future with not having full Unicode support or large indexing ability.

↧
Search

Re: ISP Limitations - MariaDB (Antelope)

May 14, 2019, 11:53 pm
$
0
0
by Alain Jacquet.  

Hi Jon

Thank you - you've saved my bacon! 

I tried this and I can now install Moodle 3.6.4..... 
I realise there will be challenges or errors, but I suppose I'm not able to avoid that with this ISP setup. 

↧
↧

Re: Error reading database - solved. BUT WHY???

May 15, 2019, 3:03 am
$
0
0
by Leon Stringer.  

Enable debugging, e.g. by adding this to config.php, change dbcollation back to utf8mb4_unicode_ci and try to log in. Hopefully you'll get more information when the error occurs. Obviously this test may cause problems if there's anyone else using the site at the time.

Also check the Environment report and attach a screenshot of any warnings.

Was the 3.4 site on the old host already Barracuda/utf8mb4_unicode_ci or was this changed as part of the migration to the new VPS?

When you see the "Error writing to database" are you logging in as a "manual" Moodle user or is this using some external authentication (e.g. external database)?

↧

Re: moodle migration

May 15, 2019, 3:05 am
$
0
0
by Luis de Vasconcelos.  

You also need to backup and copy the entire Moodledata folder to the new server.

So 3 things need to be migrated:

  1. The Moodle code
  2. The Moodle database
  3. The Moodledata folder
↧

Re: moodle migration

May 15, 2019, 3:06 am
$
0
0
by Luis de Vasconcelos.  

Did you copy the Moodledata folder (and all its contents) to the new server? That is critical.

Once you've done that and you still get errors turn Moodle Debugging up to the Developer level so that you see the error messages that get triggered. Those error message can help troubleshooting the real cause of the HTTP 500 messages. (HTTP 500 messages don't really mean anything specific, it's just the servers fancy way of saying there's a problem somewhere.)

↧

Re: Moodle install

May 15, 2019, 5:40 am
↧
↧

Re: Windows Portable Moodle and Relative Paths for 'dataroot'

May 15, 2019, 5:52 am
$
0
0
by Visvanath Ratnaweera.  

May be not what you are looking for. If the portability is priority, you should look at the https://moodlebox.net.
↧

Re: Unable to access Moodle site….

May 15, 2019, 6:11 am
$
0
0
by Michael Xile.  

I understand that, but I thought that is what noip.com and port forwarding is for...

↧
Search

Re: Error reading database - solved. BUT WHY???

May 15, 2019, 6:13 am
$
0
0
by Alain Raap.  

There is a conversion tool in your Moodle directory admin/cli/mysql_collation.php
Run this with /usr/bin/php /var/www/moodle/admin/cli/mysql_collation.php -l to see if there are different collations in the Moodle table list in your case.


I had the same problem and ran this tool with the collation that was configured in config.php (in our case utf8mb4_unicode_ci).
/usr/bin/php /var/www/moodle/admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci solved our problem.

This login problem occured after upgrading  Moodle 3.5.4+ to Moodle 3.5.5+

↧

Re: Unable to access Moodle site….

May 15, 2019, 6:16 am
$
0
0
by Michael Xile.  

I guess I never really thought that much about the security aspect. To be honest, I was so focused on the layout of Moodle, and the possibilities of weekly class notes, homework submission, etc that I never really gave much thought to some of those admin details. I just figured, even if it was running off of my nas, the moodle would be completely text-based so I didn't think bandwidth would ever be an issue.

Since I have about 300 students a semester, the cloud option doesn't seem like a possibility- I can guarantee my university won't pay for this little side project, and Im not going to pay $1,000 a year out of my own pocket.

Guess this is a dead end then. Thanks anyway for your remarks.

↧
↧

Re: Unable to access Moodle site….

May 15, 2019, 7:16 am
$
0
0
by Visvanath Ratnaweera.  

I didn't say that you can't reach your home Moodle server from the Internet. Read carefully: ' If"my ip address" in http://(my ip address)/moodle is a private IP address', then you can't.

If you are familiar with the DynDNS you can use the same technique to reach your home Moodle server - it is a web server after all. Please note that, there the URL of your server is not an IP address, but a domain name. You put that URL in your $CFG->wwwroot.
↧

Re: Moodle 3.6.1 upgrade to 3.6.4 lost use of Site Administration > admin/search.php

May 15, 2019, 8:00 am
$
0
0
by Robert Clements.  

I now have site administration access once again.  Thanks!

Robert


↧

Re: Unable to access Moodle site….

May 15, 2019, 8:24 am
$
0
0
by Ken Task.  

Home connections to an ISP typically have some device on the edge of the home network that interfaces/talks to the upstream ISP.

Home Network -> device -> ISP

Typically, (but not always) upstream ISP allocates a public ip address to the device and probably uses DHCP to set the lease of that IP address.   Lease is how long that device gets that public IP - could be forever until ISP re-cycles or some period of time - a year?.

That's what one is working with with noip or apps like that ... they inform about changes the IP address assigned to the outside interface of that device and changes DNS accordingly.

Example: yourserver.noip.com used to be XX.XX.XX.XX and is now YY.YY.YY.YY after re-cycling by upstream provider.

In config of moodle, best to use a resolvable fully qualified domain name.

Now you've mentioned 'port forwarding' ,,, that must be in your device that connects your home network to upstream provider.  Or are you using your NAS for that ... has the capability of acting as your home network router and thus gateway to the internet.   NIC 1 -> inside home network ... NIC 2 -> upstream provider.

If that is allowable by your ISP and setup correctly, in theory, what you are wanting to do should work ... but, as you said, could be further firewalls/network configs etc. in play that you cannot control.

Many of those devices (home router) have a web based interface that internal private IP addresses can access for configuration of the device.   Some have testing tools ... ping for example ... not sure I've seen DNS checking tools, but if you have such a tool, and ping'd by the fully qualified domain name setup in noip or where ever you did that, the ping has to look up the FQDN first before ping knows where to go.

All this to say ... check the device that sits on your boundary of the home network.

Also, if that works, remember to keep whatever is being accessed by the public internet up to date ... that includes your Moodle.

Good luck!

'spirit of sharing', Ken



↧
Viewing all 46891 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>