mediamosa connector throws Unable to do request, failed to login. with an external address

01Jun2012 Posted by chaoman

I have got a weird behavior to test mediamosa connector.

If I put the external IP or dynamic DNS name to the URL field in the connector test page, I got the Unable to do request, failed to login error. It works with an internal IP address such as 10.0.10.197 or localhost. I have enabled logging but the error is blank after the following info:

REST calls issued to build this page.
Show[POST] http://chaoman.dyndns.tv/login (0), (0.007 sec)

Can someone help? Thanks.

Comments

Need more info

Posted by Robert on June 1st, 2012 - 00:25

There is not enough information to help you here. You might need to check Drupal log (adminstration->reports->recent log messages), should give you a bit more information. Debugging option relates to this log (so it logs more than normal), not the output of the REST call or output of the connector.

My first guess is that your server does not allow to connect to external addresses or the URL is not going to a REST interface of MediaMosa.

Error Log and REST interface

Posted by chaoman on June 1st, 2012 - 00:43

Hi Robert,

Thank you for the quick reply. Below is the log that I see.

Type mediamosa connector
Date Thursday, May 31, 2012 - 16:41
User chaoman
Location http://chaoman.dyndns.tv/admin/mediamosa/config/connector
Referrer http://chaoman.dyndns.tv/admin/mediamosa/config/connector
Message Unable to do request, failed to login.
Severity notice
Hostname 17.246.168.11
Operations

My question is how do I confirm if the URL is not going to a REST interface? Thank you.

REST version [GET] response

Posted by chaoman on June 1st, 2012 - 00:52

I think the REST interface is working but the connector is not.

Here is a version REST call I just made. http://chaoman.dyndns.tv/version [GET]

<?xml version="1.0" encoding="UTF-8"?>

1
1
0
mediamosa_rest_call_mediamosa_version
GET
/version
1
success

601
[GET] version
3.2.1.1846
0.0416

3.2.1
1846

Next thing you need to check

Posted by Robert on June 1st, 2012 - 01:45

Next thing you need to check if the server is allowed to do call outside the server. The Drupal status page does check this and your MediaMosa status page should give you a warning that Drupal can not do call outside the server; MediaMosa uses functions inside Drupal to connect to HTTP servers. So if Drupal status page is all green, then you can exclude that as the problem. However, its still weird.

Make sure the app server is created on the MediaMosa server where you are connecting to. Also make sure the app name and the password are correct. The connector will not tell you what is wrong with the login...

To see a lot more of the connector. Enable the debugging option in the connector (you already have done that i think).

Now the trick is to enable a Drupal block. If you know Drupal, that will be easy. If not; where you connector is installed, go to drupal blocks (should find it under /mediamosa/admin/ or /admin). Its under one of the sections. Once you found blocks, enable the block called mediamosa connector debug or simular, put it in footer, or content section. Save it.

If you have done everything right, then it should now include information about the mediamosa connector and its calls its doing on the 'previous' page. Now go to the connector setup and try to save the connection. The next page should have the block filled with derbug info...

Im doing this from memory, dont have mediamosa server to look at. Im off to bed, wont be able to respond unill tomorrow. So hope you'll manage. Good luck.

Apache Alias Issue and it's fixed!

Posted by chaoman on June 3rd, 2012 - 09:50

Hi Robert,

Thank you so much for pointing out the direction. I spent my whole Saturday trying to figure out the root cause and found out it was my Apache's Alias. I recreated the entire Mediamosa backend and pasted the correct single site alias into Apache's Site-Available/default file and got it fixed. (I am running Ubuntu Server). Now my 3.2.1 is showing no errors except for new Drupal message. I will test more and let you know.

Hello Chaoman, I am facing

Posted by nickorfas on July 20th, 2012 - 14:01

Hello Chaoman,

I am facing exactly the same problem for the last couple of days.

I would be grateful if you could provide some more information about how the way you fixed this problem (setting up Mediamosa connector). I have figured out from you post that the problem was on Apache Aliases....can you be more specific about which alias did you enter and in which configuration file (ex httpd.conf,...)?

Thank you in advance,
Nickorfas

Cool, just curious, the alias

Posted by Robert on June 4th, 2012 - 10:30

Cool, just curious, the alias problem you had, was on the status page as an red error right? Always make sure the MediaMosa status page has no RED items. Although I didn't know a missing alias would break the connector login, so its good to know.