- Posts: 2
R0.25 No Longer Supported
Problem identifying Valid Trusted Host - XMLRPC
- James
- Topic Author
- Offline
- New Member
-
Less
More
15 years 9 months ago #1
by James
Problem identifying Valid Trusted Host - XMLRPC was created by James
Hi there,
Though I've had everything working nicely on my local server, I'm having the problem with the XML-RPC Error 7021 on my live site. I have looked all over the forum for answer and I think I know what the problem is. I think I need to add a trusted host IP in the Moodle back end, but I simply can't find a valid trusted host. My IP is 195.216.197.176 ( www.seren-it.co.uk ) but Moodle won't accept that. The local host details don't work there either. I've been on to my Server people, but they have been so far unhelpful. Can you suggest anything?
Though I've had everything working nicely on my local server, I'm having the problem with the XML-RPC Error 7021 on my live site. I have looked all over the forum for answer and I think I know what the problem is. I think I need to add a trusted host IP in the Moodle back end, but I simply can't find a valid trusted host. My IP is 195.216.197.176 ( www.seren-it.co.uk ) but Moodle won't accept that. The local host details don't work there either. I've been on to my Server people, but they have been so far unhelpful. Can you suggest anything?
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7926
15 years 9 months ago #2
by Antonio Durán
Replied by Antonio Durán on topic Re:Problem identifying Valid Trusted Host - XMLRPC
Hi.
First thing I would do is to test with 0.0.0.0/0
With that it should work, as it enables the world to access.
If that works, then I would try doing some debugging to find out he ip used for communication:
Write a simple script in your hosting that fetches a test page:
In that test page echo $_SERVER to see the real address being used.
Please, tell us how it goes so we can put this in the FAQ or Tips page.
Antonio
First thing I would do is to test with 0.0.0.0/0
With that it should work, as it enables the world to access.
If that works, then I would try doing some debugging to find out he ip used for communication:
Write a simple script in your hosting that fetches a test page:
Code:
file_get_contents ("http://yourserver.com/test.php");
In that test page echo $_SERVER to see the real address being used.
Please, tell us how it goes so we can put this in the FAQ or Tips page.
Antonio
Please Log in or Create an account to join the conversation.
- James
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 2
15 years 9 months ago - 15 years 9 months ago #3
by James
Replied by James on topic Re:Problem identifying Valid Trusted Host - XMLRPC
Thanks for the speedy reply. Even that 0.0.0.0/0 IP doesn't sort things. But now the error is "XML-RPC Error (7015): Unable to locate function, or function prohibited for RPC".
Perhaps something is wrong somewhere else. I've even reinstalled everything a couple of times, but maybe I've still missed something.
The server is running PHP Version 5.2.14 and XMLRPC is definitely enabled, but I don't have command line access to the server.
Perhaps something is wrong somewhere else. I've even reinstalled everything a couple of times, but maybe I've still missed something.
The server is running PHP Version 5.2.14 and XMLRPC is definitely enabled, but I don't have command line access to the server.
Last edit: 15 years 9 months ago by James.
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7926
15 years 9 months ago #4
by Antonio Durán
Replied by Antonio Durán on topic Re:Problem identifying Valid Trusted Host - XMLRPC
If I understand you correctly, when you put 0.0.0.0/0 it changed to 7015.
That means it worked
So first thing I would do is find the IP used, and then move on.
7015 error is usually caused for having errors in moodle notifications page.
That means it worked
So first thing I would do is find the IP used, and then move on.
7015 error is usually caused for having errors in moodle notifications page.
Please Log in or Create an account to join the conversation.