- Posts: 16
Can't login after changing $live_site to my domain
- Lior
- Topic Author
- Offline
- New Member
-
Less
More
14 years 11 months ago #1
by Lior
Can't login after changing $live_site to my domain was created by Lior
Hi,
I'm facing a wierd issue.
I'm using moodle 1.9+, joomla 1.5.22, joomdle 0.51.
Both moodle&Joomla seems working ok when I configured both sites using the IP of the web host:
92.XXX.YYY.ZZZ/user/moodle
92.XXX.YYY.ZZZ/user/joomla
Now, when I'm trying to configure both sites (and joomdle) using my domain:
http://www.my_domain.com/moodle
http://www.my_domain.com/joomla
I can't login to joomla:
I get errors such as:
file_get_contents(/home/user/xxx/yyy/zzz) [function.file-get-contents]: failed to open stream: No such file or directory in ...
I also have similar errors in moodle.
It seems that files are not created correctly.
I asked my host admin and he says he doesn't see any issue for his side.
What do you think?
I'm facing a wierd issue.
I'm using moodle 1.9+, joomla 1.5.22, joomdle 0.51.
Both moodle&Joomla seems working ok when I configured both sites using the IP of the web host:
92.XXX.YYY.ZZZ/user/moodle
92.XXX.YYY.ZZZ/user/joomla
Now, when I'm trying to configure both sites (and joomdle) using my domain:
http://www.my_domain.com/moodle
http://www.my_domain.com/joomla
I can't login to joomla:
I get errors such as:
file_get_contents(/home/user/xxx/yyy/zzz) [function.file-get-contents]: failed to open stream: No such file or directory in ...
I also have similar errors in moodle.
It seems that files are not created correctly.
I asked my host admin and he says he doesn't see any issue for his side.
What do you think?
Please Log in or Create an account to join the conversation.
- Lior
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 16
14 years 11 months ago #2
by Lior
Replied by Lior on topic Re: Can't login after changing $live_site to my domain
I get the following errors when trying to login:
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla_purity/plugins/user/joomdlehooks.php on line 161
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 170
Warning: fopen() [function.fopen]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Warning: fopen(/home/user/public_html/joomla/tmp/BvgSS8Gq.txt) [function.fopen]: failed to open stream: No such file or directory in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
There are many more errors/warnings... The page is stuck.
I just realized that after I reopen the FireFox, I get the homepage already sign-in (with the user I just failed to use)... That's odd...
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla_purity/plugins/user/joomdlehooks.php on line 161
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 170
Warning: fopen() [function.fopen]: Unable to access /home/user/public_html/joomla/tmp/BvgSS8Gq.txt in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Warning: fopen(/home/user/public_html/joomla/tmp/BvgSS8Gq.txt) [function.fopen]: failed to open stream: No such file or directory in /home/user/domains/my_domain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
There are many more errors/warnings... The page is stuck.
I just realized that after I reopen the FireFox, I get the homepage already sign-in (with the user I just failed to use)... That's odd...
Please Log in or Create an account to join the conversation.
- Chris
-
- Offline
- Moderator
-
14 years 11 months ago - 14 years 11 months ago #3
by Chris
Replied by Chris on topic Re: Can't login after changing $live_site to my domain
when you type in
www.mydomain.com/moodle
or /joomla what does the domain resolve to? You say it works on the IP address, but not the domain name. Thus it would appear logical that there is a problem with the domain name and how it is being resolved in the DNS. Perhaps something to do with hosted domains and how they are managing the IPs? Perhaps internal vs external IP addresses? Does your host block file_get_contents on domain names (sorry not sure if this one is possible ie block on domain name but not IP). What happens if you configure for CURL rather than file_get_contents?
Last edit: 14 years 11 months ago by Chris.
Please Log in or Create an account to join the conversation.
- Lior
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 16
14 years 11 months ago #4
by Lior
Replied by Lior on topic Re: Can't login after changing $live_site to my domain
Hi Chris,
When I type www.mydomain.com/moodle or /joomla, the domain resolves to www.mydomain.com/moodle or /joomla
My web host says if it works using the IP then it's a software issue (something with the site's code) - I'll ask him again regaring the internal/external issue.
Changing to curl resolves with the following errors:
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 161
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 170
Warning: fopen() [function.fopen]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Warning: fopen(/home/user/public_html/joomla/tmp/Kr5Ot8D5.txt) [function.fopen]: failed to open stream: No such file or directory in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Same symptom: files are not created correctly.
Regarding the mooodle: when I look into one block I created, I see that when using the pop command "copy" files are coppied whereas when using "exac" command to create files, they are not.
What do you say?
When I type www.mydomain.com/moodle or /joomla, the domain resolves to www.mydomain.com/moodle or /joomla
My web host says if it works using the IP then it's a software issue (something with the site's code) - I'll ask him again regaring the internal/external issue.
Changing to curl resolves with the following errors:
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 161
Warning: curl_setopt() [function.curl-setopt]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 170
Warning: fopen() [function.fopen]: Unable to access /home/user/public_html/joomla/tmp/Kr5Ot8D5.txt in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Warning: fopen(/home/user/public_html/joomla/tmp/Kr5Ot8D5.txt) [function.fopen]: failed to open stream: No such file or directory in /home/user/domains/mydomain.com/public_html/joomla/plugins/user/joomdlehooks.php on line 174
Same symptom: files are not created correctly.
Regarding the mooodle: when I look into one block I created, I see that when using the pop command "copy" files are coppied whereas when using "exac" command to create files, they are not.
What do you say?
Please Log in or Create an account to join the conversation.
- Lior
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 16
14 years 11 months ago #5
by Lior
Replied by Lior on topic Re: Can't login after changing $live_site to my domain
When looking into apache log, I see:
[Thu May 26 22:47:02 2011] [error] [client 81.zz.xxx.yyy] XML-RPC: xmlrpc_server::parseRequest: invalid charset encoding of received request: UTF8
Does it help?
[Thu May 26 22:47:02 2011] [error] [client 81.zz.xxx.yyy] XML-RPC: xmlrpc_server::parseRequest: invalid charset encoding of received request: UTF8
Does it help?
Please Log in or Create an account to join the conversation.
- Lior
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 16
14 years 11 months ago - 14 years 11 months ago #6
by Lior
Replied by Lior on topic Re: Can't login after changing $live_site to my domain
I changed line 175 of plugins/user/joomdlehooks.php to:
while (!feof ($f) && $f)
$f = "FALSE" and the loop is skipped.
Now the browser does not stuck and the login is ok.
What is the purpose of this loop? Can I skip it?
I tried to catch the error of the creation of the missing file:
/home/user/public_html/joomla/tmp/DNchd1B4xyz.txt
Where is it created?
How should I catch the error?
Thanks
Lior
while (!feof ($f) && $f)
$f = "FALSE" and the loop is skipped.
Now the browser does not stuck and the login is ok.
What is the purpose of this loop? Can I skip it?
I tried to catch the error of the creation of the missing file:
/home/user/public_html/joomla/tmp/DNchd1B4xyz.txt
Where is it created?
How should I catch the error?
Thanks
Lior
Last edit: 14 years 11 months ago by Lior.
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7909
14 years 11 months ago #7
by Antonio Durán
Replied by Antonio Durán on topic Re: Can't login after changing $live_site to my domain
Hi.
The loop is used to read the cookies.
That code is only used if you set "redirect-less SSO". Change it to no, and see if it works for you.
The error you posted in previous message is just a warning, nothing to do with this.
The loop is used to read the cookies.
That code is only used if you set "redirect-less SSO". Change it to no, and see if it works for you.
The error you posted in previous message is just a warning, nothing to do with this.
Please Log in or Create an account to join the conversation.