Generating a public key

Generating a public key

by Dave Powers -
Number of replies: 12
I am a newer moodler so this is probably not a big issue.

I am trying to network a few moodles on the same hosted server.

I follow the documentation but I get stuck when moodle need a public key.

2446251168_5052ba3921.jpg?v=0

I search the support forums for hours looking for a solution but everything I have tried has not worked.

Current Setup:

  • Basic hosted account at bluehost.com
  • dedicated ip
  • LINUX
  • php5
Any help would be greatly appreciated!




Average of ratings: -
In reply to Dave Powers

Re: Generating a public key

by Andrea Gregory (Gordon) -

Hi Austin wink

Have you got the correct extensions installed on the server? xmlrpc is the one that needs to be present i think...

Andrea

In reply to Andrea Gregory (Gordon)

Re: Generating a public key

by Dave Powers -
Andrea,

Thank you for the reply.

I do have xmlrpc installed, but something is still not working. It might be b/c I am on a shared server.


2458240152_634c242e86_o.jpg
In reply to Dave Powers

Re: Generating a public key

by Chris Green -
I'm in the exact same position (bluehost, setup, etc) hopefully someone can point us both in the right direction.  Seems to be a shared hosting issue though.
In reply to Chris Green

Re: Generating a public key

by Jason Bedell -
I'm stuck here. Has anyone figured this out yet?
In reply to Jason Bedell

Re: Generating a public key

by e-Learning Informàtica UPF -
hi!

The oppenssl libraries needs the openssl.cnf file to generate the keys.
Maybe your installation does not see that file....
I have to put it on
/usr/local/ssl
so that the system could see it.

Hope it helps

____
ramon loureiro
In reply to Chris Green

Re: Generating a public key

by T Brown -
I am on Bluehosts also, am trying to set up two moodles on the server, and trying to network them. My public key is also from 1969. I am sure I feel comfortable using SQL. Is there no other way? Can you only set up to networked Moodles if they are on different servers?
In reply to T Brown

Re: Generating a public key

by Nigel McNie -
You can set up networked moodles on the same server - I think the issues people are running into here are issues with Bluehost, not Moodle.

Someone might need to contact Bluehost and ask them if the XMLRPC, Curl and OpenSSL PHP extensions are installed.
In reply to Andrea Gregory (Gordon)

Re: Generating a public key

by Chris Walsh -
Dave (and others) -

Did you ever solve this issue on BlueHost? I have the exact same issue, and I'm stumped. Would love any help you can provide!

Thx.

Chris : )
In reply to Dave Powers

Re: Generating a public key

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Turn debugging on (in Site Administration=>Server=>Debugging) and then try it. I'm hoping you'll get a clue smile
In reply to Dave Powers

Re: Generating a public key

by Jeffrey Silverman -
This is a little late, but I think the solution is as follows, in SQL:

DELETE FROM mdl_config WHERE name = 'mnet_localhost_id';

(Better test that with a SQL SELECT statement first)

i.e. Delete the row in mdl_config where the name is equal to 'mnet_localhost_id'

This will force the mnet admin paage to regenerate the mnet keys. It did for me, at least, and my symptoms were exactly the same as your screenshot, (although though my hosting is a good bit different)

Later...
In reply to Jeffrey Silverman

Re: Generating a public key

by Jeffrey Silverman -
Actually, you also have to reset the mnet localhost id to the new mnet key id. This is a bug (See MDL-14176 )

For example:

UPDATE mdl_user SET mnethostid = 3 WHERE mnethostid = 1;

(Assuming the newly generated id for the new key is "3" and the old one was "1")

You can find out what the id of the new key is by looking at the mnet_host table:

SELECT * FROM mdl_mnet_host;


Later...
In reply to Jeffrey Silverman

Re: Generating a public key

by Chris Walsh -
These two fixes worked! It turns out, it wasn't a Blue Host issues at all. Moodle just needed some DB cleanup like Jeffrey noted. Once his two fixes were complete, it all worked. Woohoo!

Thx JS!

Chris : )