We are facing a moodle access problem at the university. Many users have reported that they are unable to access the platform, while others are accessing normally, it appears the message "This site is not available currently.". I already checked with the IT Department and they told me that everything is normal. Moodle version is 3.3.4. Have you faced this problem yet?
Moodle generates that message when you have set up the IP Blocker and Moodle encounters an IP that is not permitted.
Check your IP Blocker settings - see IP_blocker
Note especially...
"If there are entries present in the Blocked IP List, any hosts for which Moodle cannot determine the IP address will be blocked by default. For example, hosts that are behind a web proxy server which does not pass the HTTP headers containing the remote IP address information."
Hi,
No, there's nothing in this box.
The ONLY place in the code (and I'm assuming that you have not changed core code) where that message could be displayed is when either $CFG->blockedip or $CFG->allowedip are set.
If they are not set on the admin page, then they must be set in the config.php file.
I haven't changed the core code.
Can this problem be associated with multiple access, or some configuration in php?
Have you checked your config.php file for those two $CFG settings?
One of those being enabled is the only thing that would cause this particular message. Assuming of course it is coming from Moodle and not somewhere else
If one were to use Google to search for the issue, one can see that it happens with browsers, with other web sites/applications, etc. And, there's not one solution for all.
Moodle screens could be yellow in background with an oval box that contains information ... like the 'Site Maintenace Mode' notification screen.
So wonder if your students ... one or two .. couldn't provide you with screen shots ... when/if it happens.
The other factors ... network comes before application ... the students that have the issue, what are they using (FireFox/Chrome/Edge) ... are they using smartphone or tablet or laptop? Where are the students located? (StarBucks, home, wireless on the campus, etc.).
When I've had similar issues, I created a separate 'troubles' directory and index.html page that's outside of Moodle code ... url like https://site/troubles/. All it had in it. was an image saying thanks. If one views the web server access logs, normally those logs are set to show things like IP address and browser information - which is useful information when attempting to troubleshoot such issues. That's IF user can get there.
Example ... user kept complaining to local IT department about same problem ... when asked to hit the 'troubles' page, logs showed user was using a Windows Smart Phone. Now one has some info for research.
If user can't get there at all ... it's a networking issue ... has to be ... ask the more technically aware students having the problem to do some network testing ... look up the Moodle server FQDN using command line nslookup ... ping the ip address of the moodle server (which may fail due to network restrictions on pings). If student is kinda into networking, they could use a tool like 'nmap' which could attempt to connect to the IP address of the moodle server and if using port options, display if port 80 or 443 (for https access) are open.
A Troubles web page ... assuming they can get to the moodle server.
coderoot troubles direcectory
index.html flie
<html>
<head>Troubles?</head>
<body>
<h1>Thanks! Will look into it.</h1>
</body>
</html>
Server could be set for multiple logging ... like ssl_request_log
/var/log/httpd/ssl_request_log:[17/Jul/2018:10:01:05 -0500] IPADRESSOFCLIENT TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "GET /troubles/ HTTP/1.1" 91
Might be important if client were using a device/handheld/etc. that couldn't talk TLSv1.2 ... they all should be now!
/var/log/httpd/access_log:CLIENTIPADDRESS - - [17/Jul/2018:10:06:29 -0500] "GET /troubles/ HTTP/1.1" 200 91 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0"
Above might indicate client problem ... OLD OS or old browser.
'spirit of sharing', Ken
It would be quite a coincidence if some other system was producing *exactly* the same error message. But stranger things...
However, yes, a screen shot would settle it once and for all.
Thanks for your help, we're investigating if it's a networking issue at the university. It's very strange, because not everyone has this problem.
They are trying to access at home, using wi-fi, and the problem happens with all browsers on laptop and smartphone too.
It works if they use 4g mobile internet (but it's unstable)
Some users can access using google DNS on laptop. I've attached a moodle screen shot.
![Attachment 20180712_104111[4726].jpg](https://moodle.org/pluginfile.php/143/mod_forum/attachment/1505677/20180712_104111%5B4726%5D.jpg?forcedownload=1)
That's not a Moodle error screen at all. Browser error.
Concept in networking ... to paraphrase ... not all roads run straight to Rome!
Home connection ... laptop or smartphone connected to the *home* wireless/cable modem which is wired via cable -> cable provider. That's one route/network. That's one road to Rome!
Home connection ... smartphone using 4G is connecting to the wireless provider ... here in USA that could be companies like AT&T, Verizon, BoostMobile etc. ... so that's yet another network ... and thus a different road to Rome.
Not getting there at all could be DNS issue ... DNS is provided by however one connects upstream from the home.
Now you mentioned google DNS .... yes, in laptops etc. home computers one can set additional DNS servers to the DNS servers provided by upstream service. Google offers public (anyone can use DNS resolvers) 8.8.8.8
Rather than re-write ... check this page out and see if you cannot EMail the link to those having problems at home:
https://www.howtogeek.com/164981/how-to-switch-to-opendns-or-google-dns-to-speed-up-web-browsing/
I can't quite make out the URL to your moodle or I would do some DNS/traceroutes, etc. from here.
That troubles folder idea on the moodle won't work cause they are not hitting the server at all ... but, here's another quick test ... is there another server (not your Moodle) on the same physical network as the Moodle server? School library, for example. library.something.edu.br ... moodle server is @ elearning.something.edu.br.
Can those users hit library.something.edu.br? Remember now to be a valid test ... library server and moodle server *have to be* on same physical IP addressed network.
On Windows isn't there a way to rebuild the TCP/IP stack? (Google that).
Have the users updated their browser ... Chrome, as of recent, has had some 'networking' issues. (Google that one too!)
If you private message me the URL to your Moodle, I'll do some network testing from here, if you like. Might see something that I could share back or not ... dunno.
'spirit of sharing', Ken
A coincidence indeed