## General help

Hi everyone,

When I click Users > Accounts > Upload Users , I recieve the error message below.  It seems that I can click around other locations in the site.

Response Error.

Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

I'm on Moodle 1.9.9 (Build: 20100609)  with PHP 5.1

What information do you need?

Average of ratings: -

I talked to the hosting company, and they said it's because the upload.php script is calling a file on another server.  Is there a way to easily compare the upload.php file (and all the files it includes) to make sure they are the same as the standard Moodle 1.9.9 install?

We have a restore point for every day for the last 7 days, but I'm trying to avoid that.

Average of ratings: -

BTW -today the error message changed from "502 bad gateway" to "Page cannot be displayed"  The files are there though - I just downloaded them via FTP.

The hosting company said i should check the log files in /var/httpd

Maybe that will show what files were changed...

If anyone has any tips, I'd love to hear them!  I'll keep documenting progress here.

Average of ratings: -

Couple more things ... have you tried a different browser? (although the bad gateway error isn't tied to a browser and can happen to any browser/any OS).

Mind disclosing who the hosting provider is?

Have any addons or using authentication methods that would require talking to another server when it comes to users?  LDAP?

'spirit of sharing', Ken

Average of ratings: -

What makes you think the file was changed?

I would switch on Debugging and see if you get any additional messages that might pin this down. I'm a bit sceptical about your host's explanation.

Average of ratings: -

There are only these 'upload.php' files in a 1.9.19+:

uploaduser.php file has the following required:

require('../config.php');
require_once($CFG->libdir.'/adminlib.php'); require_once($CFG->libdir.'/csvlib.class.php');
require_once($CFG->dirroot.'/user/profile/lib.php'); require_once('uploaduser_form.php'); If your hosting provider says 'calling file on another server', did they happen to mention the location/url of that server? 'spirit of sharing', Ken Average of ratings: - Re: 502 Bad Gateway - clicking upload users About acquiring old code (1.9.9 is old!). One could get the entire package (1.9.9+ at least) by using git on a local machine - not server. git log -p version.php Will show a long listing of info on releases. Scroll through the listing until one sees a release for your 1.9.9 (+ is ok it's close enough). Note the commit line below. commit 813d4754fdc8601541f51c885820f473970c8b6d Author: Moodle Robot <martin@moodle.com> Date: Sun Oct 24 00:55:27 2010 +0000 Updated the 19 build version to 20101024 diff --git a/version.php b/version.php index 73c2fe8..575389c 100644 --- a/version.php +++ b/version.php @@ -10,6 +10,6 @@ // X = release number 1.9.[0,1,2,3,4,5...] // Y.YY = micro-increments between releases -$release = '1.9.9+ (Build: 20101023)';     // Human-friendly version name
+    $release = '1.9.9+ (Build: 20101024)'; // Human-friendly version name To acquire all the 1.9.9+ code in a directory (then one could compare files from server): git clone git://git.moodle.org/moodle.git moodle199 cd moodle199 git branch --track MOODLE_19_STABLE origin/MOODLE_19_STABLE git checkout 813d4754fdc8601541f51c885820f473970c8b6d fgrep release version.php should show: // X = release number 1.9.[0,1,2,3,4,5...] // Y.YY = micro-increments between releases$release = '1.9.9+ (Build: 20101024)';     // Human-friendly version name

Am not at all certain that any files on your system has changed, but ....

Might check into:

Link above list 12 things to do/try, etc.

'spirit of sharing', Ken

Average of ratings: -

Replacing the file didn't fix it, but restarting the server did fix it.

Thank you all for your posts.  Yes, I did mean the file in the admin directory.  I was just stating how to navigate using the interface.

Turning on debugging didn't provide additional info because it wouldn't even show the page.

Thanks for the tip on 1.9.9 git.

The hosting company said to read the log files but before I did that, we decided to just restart the server to see what happened.  Restarting fixed it!!

Average of ratings: -