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

Re: Moodle on subdomain but wish to use login mechanism of main site.

May 20, 2021, 12:07 am
$
0
0
by Howard Miller.  

Really... this is when you probably should be looking at a separate user database such as an LDAP (e.g. Active Directory) setup for your users. Then both your Moodle sites would authenticate against the same database. There are a lot of optional auth plugins for Moodle (https://moodle.org/plugins/browse.php?list=category&id=21). I couldn't see anything that looks useful for authenticating one site against another.

You still have MNET which potentially provides SSO between multiple Moodle sites. That might be useful (https://docs.moodle.org/311/en/MNet)
↧
Search

Re: Bigbluebuttonbn broke after updating to 3.11

May 20, 2021, 3:54 am
$
0
0
by Igor Neumann.  

The github version worked like a charm... MANY THANKS!

For someone with the same problem finding this, just download the zip and upload as is.


↧
↧

Error 404

May 20, 2021, 4:48 am
$
0
0
by Shaune Beyleveldt.  

Hi - Ive been looking all over and cant seem to find the answer on how to resolve the below issue

Local LAN all works well - Its when I try and access via WWW - Port forwarding done 80 / 443 


Any Ideas?


↧

Re: Error 404

May 20, 2021, 4:48 am
$
0
0
by Shaune Beyleveldt.  

Also im not sure if this is the right place to ask this?
↧

Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 5:40 am
$
0
0
by Dan O'Reilly.  

I just upgraded my development Moodle site from 3.10 to 3.11.  This is a MAMP installation on a MacBook running macOS Big Sur.  Generally, there were few problems in the upgrade to 3.11, though I had to make some changes to the php.ini file.  However, I now notice that HTML <hr> type lines divide activities.  (See uploaded image.)  Is there a way to turn these new lines off (I cannot find any mention in the documentation)?

↧
↧

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 6:22 am
$
0
0
by Helen Foster.  

Hi Dan,

In Moodle 3.11, activity dates and completion conditions can be shown on the course page. As you've noticed, the lines divide activities so that you can see which activity any dates or completion conditions apply to.

However, you can choose to not show activity dates and completion conditions on the course page by setting 'Show activity dates' and 'Show activity completion conditions' to No in the course settings. If both are set to No, then the lines will disappear.

↧

Re: Error 404

May 20, 2021, 6:49 am
$
0
0
by Howard Miller.  

It's almost certainly a problem with youe Apache setup. I doubt that helps much. It's not really a Moodle problem.
↧

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 7:57 am
$
0
0
by Dan O'Reilly.  

Hi Helen,

Thanks for the information. However, as I am using completion conditions on some of my activities, e.g., quizzes and lectures, I need to keep 'Show activity completion conditions' to Yes. I guess I will have to incorporate the lines into my design in some manner.

Dan
↧
Search

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 8:12 am
$
0
0
by Rick Jerz.  

I used the following CSS to revert my activities and resources back to how they looked in Moodle 3.10.


/* Moodle 3.11 changes
Each activity had more space and a line under it. Perhaps something involving new accessibility? */
.section li.activity.hasinfo {
border-bottom: 0px solid #dee2e6;
padding-top: 0rem;
padding-bottom: .5rem;}
↧
↧

Re: Error 404

May 20, 2021, 9:19 am
$
0
0
by Visvanath Ratnaweera.  

Upload any test.html file to your Moodle code directory (where the config.php) is, and see whether yoursite/test.html brings you the HTML rendered. If not, the issue is definitely with the web server or the network setup.
↧

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 11:57 am
$
0
0
by Dan O'Reilly.  

Rick,

Great code! Works like a charm to fix my visual dilemma.

Thanks
↧

No moodledata/sessions/sess_* files after migration

May 20, 2021, 12:34 pm
$
0
0
by Pablo Hernández.  

Hello Moodle Comunity.  My first post, happy to be here.

Hope you can help me out solving a concern.

I recently migrated my Moodle 3.10.3+ (Build: 20210430) site from shared hosting to VPS (LAMP->LAMP). I did so by following instructions at https://docs.moodle.org/310/en/Moodle_migration.

Apart from one particular issue (discussion for another time) everything seems to be life-as-usual. New service has been live for the past few days.  Moodle environment check page (admin/environment.php?version=3.10.3) is A-OK, performance is good and classes are taking place as usual.

As per Moodle recommendation, cache, localcache, sessions, temp and trashdir folders were not migrated.

For everything else, other than adjusting db and paths in config.php, it was pretty much copy+paste.

However, despite the site being operational, I noticed there are no sess_* files at moodledata/sessions/ folder (actually, no files at all) in the new server, while there were many in the original one (not migrated).

If my understanding is correct, default session driver is file, and default destination is moodledata/sessions.  There were no $CFG entries for session handling in the original config.php file, and there are none in the new config.php.  There are session records in mdl_sessions database table, and sessdata field/column is NULL (I believe this is in-line with file session driver, right?).  I'm overseeing a few other Moodle installations, none with any session-related $CFG entries, all with sess_* files on moodletada/sessions/ folder (even after similar migrations).

There are no user reports of issues or errors, nor any particularly interesting log entries other than a handful of invalid sesskey entries (debugging currently set to 'ALL').  Also, no sessions seem to be aborted prematurely.

Out of curiosity I changed moodledata/sessions/ folder permissions, and the site stopped working immediately claiming there was some configuration error (sorry, did not take note of the exact message). This makes me think Moodle is aware of the folder, and is somehow accessing it, so I reverted back the permissions.

Given the fact sess_* files exist in the old server and site was copied over with minimal mandatory config changes, should I worry no sess_* files are being created? If so, any ideas what would need to be done for the files to be created?  I've checked and re-checked my configuration and searched on-line forums and articles, but haven't been able to find an answer.  What am I missing?

My current configuration is:
* Moodle 3.10.3+ (Build: 20210430)
* Ubuntu 20.04 LTS (Kernel 5.4.0-73-generic)
* Apache/2.4.46 (Unix)
* MySQL Community Server 5.7.33
* PHP 7.4.19 (Zend Engine v3.4.0, Zend OPcache v7.4.19)

Moodle was originally installed from git, and transferred to new server along with repository. No update/upgrade was done during or after the migration.

For the time being, no Redis, memcached or any non-standard module in use.

Any ideas are greatly appreciated.

Pablo

↧

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 1:22 pm
$
0
0
by Rick Jerz.  

Good to hear. Probably the “solid #dee2e6” can go.
↧
↧

Re: No moodledata/sessions/sess_* files after migration

May 20, 2021, 2:09 pm
$
0
0
by Leon Stringer.  

It sounds odd to me.

Under Site administration ▸ Server ▸ Session handling Is Use database for session information off (recommended) or on?

In Site administration ▸ Server ▸ PHP info what's the local value for session.save_path?

↧

Re: No moodledata/sessions/sess_* files after migration

May 20, 2021, 2:55 pm
$
0
0
by Pablo Hernández.  

Right on spot! Thanks a million Leon.

Use database for session information is off (unchecked).

However, PHP session.save_path is pointing to ~/tmp/, where I could finally find the sess_* files (thought I had searched my fs before but obviously failed).

Two additional questions if I may:
1) Now that I add session.save_path to my google searches I see there are tons of resources, from changing php.ini to adding $CFG entries to config.php. Any best practices you could please recommend?

2) My pre-migration server had 238 session files in total after a few months of service, the new server already has 5,520 session files (and growing by the minute) after only 4 days. Files are +/- evenly distributed by date, with some ~1,380 files per day. I only have 476 registered users.
↧
Search

Re: Moodle 3.11 Change in the display of activity blocks

May 20, 2021, 2:56 pm
$
0
0
by Dan O'Reilly.  

You are right. I removed that bit of code and it still does what I want. 👍
↧

Re: No moodledata/sessions/sess_* files after migration

May 20, 2021, 3:57 pm
$
0
0
by Ken Task.  

The move from shared to a VPS (dedicated server for your purporses) means the VPS has a different IP address ... all it's own ... and that you probably had also to change DNS ... fully qualified domain name (like sos.somesite.net) repointed to the IP address of the new hosting.

If that new_IP_to_you address had been used by another customer/site, then what you might be witnessing is folks/machines seeking old site.

Is your site forcing login before viewing anything?  Are there courses open to guest?

The place to look to see if it's mistaken traffic or pokes and probes is your web servers access and error logs ... especially the latter.   Does new server use phpmyadmin?   I see scans for that all the time on my servers ... especially when there has been a new release of Phpmyadmin.   Other scans as well ... looking to see if there is a word press on server or some other application.

Might take the time to review/read/re-read:

https://docs.moodle.org/311/en/Security_recommendations

'SoS', Ken

↧
↧

Re: No moodledata/sessions/sess_* files after migration

May 20, 2021, 4:36 pm
$
0
0
by Pablo Hernández.  

You are correct, VPS has a different IP address than before and we changed DNS so our domain is repointed to the new server.

The site is enforcing HTTPS, forcing login and nothing is open to guest (guest is actually disabled).

I failed to mentally link the fact of folks/machines seeking old sites. There's been thousands of invalid logging attempts (O/S level, not Moodle), and some IPs blocked by the firewall already. I'm working with the provider on this subject trying to make the server as secure as possible.

Thank you for the reminder on the Security Recommendations page. I'll go over it once more, and make sure everything is right in place.

Leon, Ken, thanks a million. You have been of great help.
↧

Re: No moodledata/sessions/sess_* files after migration

May 21, 2021, 4:00 am
$
0
0
by Leon Stringer.  

Re 1: Moodle explicitly sets PHP's session.save_path for itself. Unless you set $CFG->session_file_save_path to /tmp then I think Moodle will only store session files in moodledata/sessions. The only similar problem I've seen was where SELinux prevented writing to moodledata/sessions but in that instance session_start() failed with an error and logins wouldn't work.

Were you able to identify why session files were being written to /tmp?

If not, have you checked the web server error log for any relevant messages?

Note that if you make changes to session storage the site's users may all be logged out.

Re 2: Similar to what Ken says, Moodle normally explicitly stores PHP session files in moodledata/sessions but any other sites would use the session.save_path value from php.ini. Also (I think) any access to a Moodle page would create a session file. The cron removes old session files.

↧

Re: No moodledata/sessions/sess_* files after migration

May 21, 2021, 11:57 am
$
0
0
by Pablo Hernández.  

Re 1: I added $CFG->session_file_save_path = $CFG->dataroot.'/sessions'; to my config.php last night, even restarted the web server, but session files are still being sent to ~/tmp folder.  I will try tonight setting a hard path and see if it changes (no day-time changes to avoid user impact).  I would prefer adjusting Moodle settings rather than PHP settings, as I might end up having more than one Moodle instance in the same server and I'd prefer per-instance session file segregation (not crucial but nice-to-have).


To be clear, files are not being sent to the ("main") /tmp folder, but a tmp subfolder within the user's home folder (hence the ~/tmp notation). Even though it is a dedicated server, I'm using a dedicated user account with just about the necessary permissions.  Account was created through DirectAdmin panel, which creates specific per-account settings, including session.save_path, which I expected Moodle to override.

I'll report back after using a hard path and doing more research on the subject.

Re 2: It seems two session files are created per visitor (pre/post login). As Ken suggested, I'm getting hundreds/thousands of visitors looking for an old service running on the IP address I was assigned on this new VPS.  This has not been a real issue so far, and I expect unwanted visitors to decrease over time.

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