run nmap Google
it will then try to see if it can see that port.
our lea blocks port 443 by default and you have to use the upstream proxy.
I have installed the plugin from moodlerooms but I keep gettings a connection error...
My moodle is installed on ubuntu server and goes through the LA firewall so I am wondering if I can do any checks on the ubuntu box to see if it's something I need to change on it?Google Apps error: Unable to Connect to ssl://www.google.com:443. Error #110: Connection timed out
Has anyone else used this successfully?
Thanks for that.
i ran it and got this
Not sure what to make of it yet though!Starting Nmap 4.53 ( Insecure.Org - Nmap Free Security Scanner, Tools & Hacking resources ) at 2011-04-05 12:03 BST
Warning: Hostname Google resolves to 6 IPs. Using 220.127.116.11.
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 2.031 seconds
Yes we have a proxy server that we have to go through!
If not then you need to ask the lea to open up port 443 to that specific ip address i would presume but without know the full setup i'm not sure.
When I use nmap -PN Google I get no response, the command line stays blank.
I'm starting to think now that there is nothing wrong with my moodle install but something else is to blame?
Last edited by reggiep; 5th April 2011 at 01:35 PM.
I'm going to look at this further.
pings seem to be blocked via our LA firewall.Starting Nmap 4.53 ( Insecure.Org - Nmap Free Security Scanner, Tools & Hacking resources ) at 2011-04-05 12:12 BST
Warning: Hostname Google resolves to 6 IPs. Using 18.104.22.168.
All 1714 scanned ports on bru01m01-in-f147.1e100.net (22.214.171.124) are filtered
My gateway seems fine.
We had to get the LEA to open up port 443 to Google for traffic from our webserver to get single sign-on to function in Moodle. We tried setting the proxy in Moodle and system wide on the server and neither worked.
It will almost certainly be a proxy issue. PHP Curl will need this setting otherwise it won't be able to pass through the proxy to authenticate with Google. Either that or as mentioned above, a system proxy may fix the issue - though I am no *nix expert.
I can't find anywhere where you can globally set the proxy for cURL in ubuntu. I don't think it is possible.
I have found the page but it doesn't really help as I can't work out what it is telling me to edit!
There are currently 1 users browsing this thread. (0 members and 1 guests)