Joomla URL seems to be misconfigured in Joomdle auth plugin

This post is a continuation of the issue below: our inability to reliably sell bundles.

www.joomdle.com/en/forum/r09-support/925...t-setting-joomla-grp

I convinced Leslie to let me try upgrading everything to see whether this resolves the problem, but now I am stuck because I am getting the above named error on my scratch server:

Amazon EC2 instance with Bitnami LAMP stack
Joomla 2.5.11
Moodle 2.4.4
Joomdle 0.91

I copied everything from Leslie's live server to an Amazon EC2 instance because I was unwilling to disrupt her live server to do the upgrades. I discovered that on an Amazon EC2 instance Joomdle does not like anything other than www.something.com as a URL in its configuration. I tried the EC2 url ec2-xxx-xxx-xxx-xxx.us-west-2.compute.amazonaws.com and I even tried an xxx.xxx.xxx.xxx IP address. It wasn't until I assigned a domain name to my scratch server that I could get Joomdle to work at all.

I have installed the upgrade to Moodle twice, and the AUTH and ENROL Joomdle plugins twice, and reissued tokens twice. I have uninstalled and reinstalled Joomdle 3 times, and I still get this error:

Joomla URL seems to be misconfigured in Joomdle auth plugin in Moodle

I followed the instructions on this page:

• Make sure you include http:// --> DID
• Check Joomla multi-language configuration and enter appropiate parameters in Moodle side if necessary --> No extra language packs installed, just the default EN.
• Check any mod_security rules that may deny XMLRPC traffic --> Don't know where to find this, can you elaborate?
• Disable any Joomla security extensions you may have installed --> NONE

Re-check your Joomla URL in Joomdle auth plugin configuration, in Joomdle auth plugin in Moodle.
--> Because I am setting this up on a scratch server, I couldn't use Leslie's main domain name, I had to substitute something else. I put the substitute domain name in the config.php for Moodle, in configuration.php for Joomla, in the Joomdle AUTH plugin, and in the Joomdle configuration and I am still getting this error.

Is Joomdle reading the domain name from somewhere else? Is that why I am still getting this error despite installing multiple times with the configuration described above?

I am at my wits end. What can I do to make SURE this is working on my scratch server before I copy everything back to her Live server?

Toolie

You will probably not like this idea as it requires additional work but what I do in similar situations is copy my entire live server to my local PC. Then only my local PC I add an entry in the hosts file to point my mydomain.com to 127.0.0.1.

This will allow me to configure joomla, moodle and joomdle exactly as I would on the production environment with exception of the "/" directions which doesn't seem to mater as the browser follows the PC.

Also, this assumes that you have all the php libraries installed like curl, etc.

Note: I use windows 7 locally with XAMPP but you could do this with any pc / server.

Thanks for your reply Chris. Instead I moved the site to a standard hosting plan (like the one she's on already) in case there's something quirky about the Amazon EC2 LAMP stack I chose to use -- I can figure that out later. I'm not done with that move, and I'm now 3 DAYS behind schedule because of this error.

Meanwhile, can you answer these two questions from the thread above?

Is Joomdle reading the domain name from somewhere else? Is that why I am still getting this error despite installing multiple times with the configuration described above?

Toolie

No. Most likely you are getting the error because some differences in server configuration.

It is now a month later, and I've installed a copy of Leslie's site on a brand new standard hosting plan.

Joomla 2.5.11
Moodle 2.4.4
PHP 5.3.26
MySQL 5.5
Joomdle 0.92

I have checked every setting 3 times, and I continue to get the error. This is the end if we can't find a resolution: I will lose Leslie as a client over this.

I don't know how to communicate to you the hundreds of hours I've spent on this issue. Since I'm not the only one who has for the last year run into this issue without a resolution, can you please tell us where to look to debug the problem on our individual servers? I've seen posts on LinkedIn and Moodle.org from people looking for answers to this problem.

Do you need for interested parties to contribute cash so you have time to figure this out? I bet if I asked, other interested users would chip in just to get this fixed, finally.

What do you say Antonio, will you help us?

Toolie

This is not a problem you can "fix".

This error tells you that there is a problem with your server configuraiton*, so you can try to fix that instead.
Obiously, debugging the problem requires some coding and web services knowlegde, so it is normal that some people cannot solve it.

For those who can't or don't want to deal with it themselves, we offer professional installation services, as you know.

*Examples are: PHP errors being returned, dns problems, firewall and other security measures....

Let's reconsider the situation: you have a particular PHP/MySQL setup that you are using which makes everything work perfectly for you. No doubt there are differences in hosting companies; the fact that you're in Europe and I'm in the USA may have everything to do with differences in configuration.

• Do you develop on a Windows machine with WAMP server and then upload to run tests?
• Do you develop on a Windows machine and only test on a Linux configuration? If so, which flavor of Linux?
• Can you point me to the hosting company that you use so that I can compare PHP/MySQL configurations?
• What else can you safely disclose about your setup that might help me identify where my configuration errors are?

I have read the system requirements and my hosting company's configurations meet them, so there must be something else in your configuration that is different than mine. I'd appreciate your configuration specifics over and above system requirements so that we can proceed with fixing our configuration to match. Feel free to use the email address in my profile if you'd prefer to respond privately in email.

Thanks,

Toolie

Hi there,

That is simple and not so simple to answer.

We host in USA (shared hostgator) and Singapore (dedicated server centos). We develop in Spain ,USA and Singapore.

We have successfully installed in numerous countries and hosting situations with many versions of Joomla, Moodle, PHP and MySQL. Antonio develops and tests in Unix. I test in Windows using XAMPP.

As a general rule of thumb the minimum MYSQL requirement is that of Joomla and/or Moodle not of Joomdle. Remember Joomdle sits inside Joomla and Moodle not on its own thus the technical requirements are for Joomla and Moodle. The area of challenge for most is the interface / connectivity between the servers. Ie not being able to connect to each other if different servers or being 'blocked' from connecting to itself when on the same server / domain.

Generally as per Antonio's earlier post, connectivity problems are related to:
- protocols not being installed and/or configured ie curl, xml, etc.
- routers blocking particular TCP ports
- incorrect IP address since servers (especially shared hosted servers) have a different internal versus external IP address
- improper DNS configurations and/or mod_rewrite rules

OK, we're at a point where we're going to have to hire you to fix this. I have done everything you and your documentation have said to do, twice. I will contact you separately.

Toolie