The temporary file isn't there for CURL!

Hi,

I want to user SSO for login into Joomla and Moodle.
But... when I active the SSO I get the error 'The temporary file isn't there for CURL!' when people try to login.
ofcourse I can disable the SSO but when I do that, logging in and out of Joomla goes wrong. I can login, but when I logout, I am staying logged in in Moodle
If I login in joomla with a different account, I am still logged in as the previous user.

what can I do about that?

Thanks!

That message is not coming from Joomdle but is possible that the message appears when Joomla tries to use CURL. Do you have green check marks for all items in the Joomdle system health check?

Given that the error message is not from Joomdle, it could be a curl implementation or php installation issue. Are you on a shared hosting server, dedicated server, VPS?

What versions of Joomla, Joomdle and Moodle? What is your server OS? PHP version?

Hi Chris,

thanks for your response!

I have one red mark in the Joomdle system healt check:
'Moodle to Joomla HTTP connectivity, Moodle cannot connect to Joomla'
despite this error everthing seems to work fine.
I am on a shared hosting (Siteground)
Joomla 3.4.3 Moodle 2.9.1+, PHP 5.5.27
But... there is a very strange thing. The Curl error is on the production website. I have a test site (in a subdomain of the productionsite) and the curl error does not exist there! The Joomdle system check also gives the error that Moodle cannot connect.

The production and test website are identical to each other (copy)

any idea?

thanks,
jose

If the test site is working without a problem ie no error message and it is on the same server ie only difference is the folders / path, then this is likely to be your issue because the two servers (production and test) cannot be 100% copies. The configuration (url) must at least be different to be working properly.

You can copy your path configurations in here if you like, perhaps changing the domain name, for us to review.

Hi Chris, sure but what path config do you need? The general configuration of Joomdle in Joomla for both installations?

> 'Moodle to Joomla HTTP connectivity, Moodle cannot connect to Joomla'
despite this error everthing seems to work fine.

This cannot be true. You have not noticed the problems but they sure are there : indeed the CURL error is most likely caused by this.

So, you need to fix system check before doing anything else.

Hi,

I fixed the 'Moodle to Joomla HTTP connectivity, Moodle cannot connect to Joomla' error. This was caused by too strict permissions within admin tools.
I solved that, so the system check is all green!

The only thing that is wrong is not able to activate SSO because then, when people login, they get the error : The temporary file isn't there for CURL!
After that they are logged in in Joomla and in Moodle. Logging out goes perfectly too. The only thing is the error right after logging in.
what is this error? what temporary file are we talking about?
I am totally in the dark here.

As I said, disable SSO is not my solution, I need SSO.
How can I get rid of it?

thanks,
jose

> The only thing that is wrong is not able to activate SSO because then, when people login, they get the error : The temporary file isn't there for CURL!

Try disabling redirect-less SSO. This does not disable SSO, it just use a different method to do it.

Hi Antonio,

If I disable redirect-less SSO, logging in and out of Joomla goes wrong. I can login, but when I logout, I am staying logged in, in joomla
If I login in joomla with a different account, I am still logged in as the previous user. If I can solve this, I can use it, but now I cannot.
Any solution on this?

If not, can you tell me what the temporary file or folder is, that the error : The temporary file isn't there for CURL!' is reffering to?

> If I disable redirect-less SSO, logging in and out of Joomla goes wrong
That's strange, as this method works for most people. This must be related to some specific configuration on your server.

As for the CURL error: it is shown when curl file is not written, due to file permissions or the contents being empty.
This error should not really happen, so it is probably related to your problems using the other SSO method.

You could also try disabling admintools to check if your problems are related to it.