Unable to login into the public ip Server URL from remote machine

You don't say which version of Xibo you're using.

Clear your browser file and session cache. Something is serving you an old version of that form.

Look at how your server gets to the internet - is there a reverse proxy, load balancer or similar between you and the server?

We really prefer people ask questions in Launchpad Answers before filing a bug. That way we don't clutter the bug tracker with non-bugs - and that keeps the devs happy :)

Cheers

Alex

I've just spoken to Dan about this.

You have the longest UserAgent string I've ever seen:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; GTB6; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; FDM; .NET CLR 3.5.30729; .NET CLR 3.0.30729; OfficeLiveConnector.1.4; OfficeLivePatch.1.3

The browser session code we use ties your session to a session id and your user agent. Can you try with Firefox or Chrome and see if they let you log in OK?

Cheers

Alex

Hi Alex,

Apologies for raising as defect which does not look like it. I will make
sure that wont happen again. My team and I are working on implementation
looks quite impressive.

I logged in okay with Chrome. Its looks like its the problem only with the
IE. I am using IE8 (updated to latest) . While I am a big fan of windows, I
have to say they let me down this time :)

Thanks for your quick response. Any chance for a java client :)

Appreciate your time.

Cheers
Venkat

----- Original Message -----
From: "Alex Harrington" <email address hidden>
To: <email address hidden>
Sent: Wednesday, February 10, 2010 2:59 AM
Subject: [Bug 519352] Re: Unable to login into the public ip Server URL
fromremote machine

I've just spoken to Dan about this.

You have the longest UserAgent string I've ever seen:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; GTB6;
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR
2.0.50727; .NET CLR 1.1.4322; FDM; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
OfficeLiveConnector.1.4; OfficeLivePatch.1.3

The browser session code we use ties your session to a session id and
your user agent. Can you try with Firefox or Chrome and see if they let
you log in OK?

Cheers

Alex

--
Unable to login into the public ip Server URL from remote machine
https://bugs.launchpad.net/bugs/519352
You received this bug notification because you are a direct subscriber
of the bug.

Status in Xibo Open Source Digital Signage: Incomplete

Bug description:

Firstly Great software. Its heaps better than I expected. I installed it
okay had few issues resolved it :)

I get the following error when i try and login into the Server from publicip
(say http://123.123.123.123:8080/xibo/index.php). I have more than one
machines at home where the server is located in one and i am using client
for another.

Server Environment
-------------------------
Dell Precision Server /Windows XP Pro SP3/4GBRam/Apache2.2/Php5/Mysql5.1

Client Environment
------------------------
Dell Optiplux gx520 /Windows XP Pro SP3/2GBRam/128Mb Graphics./Xiboclient

I get the following error when i try to login from the client directly using
public ip. Hope its not some configuration issue. I tried to see this
token is generated randomly could not get time to go further its already
2:30am here . Any help is highly appreciated. I am happy to provide any
further information needed.

Error Description.

Form token incorrect from: XXX.XXX.XXX.XXX with token
[2e72737042fc22dcad176044ca821d56]

The query [INSERT INTO log (logdate, type, page, function, message,
RequestUri, RemoteAddr, UserAgent, UserID, displayID, scheduleID, layoutID,
mediaID) VALUES ('2010-02-10 01:56:36','error', '', '', 'Form token
incorrect from: XXX.XXX.XXX.XXX with token
[2e72737042fc22dcad176044ca821d56]',
'/xibo/index.php?q=login&amp;referingPage=index', 'xxx.xxx.xxx.xxx',
'Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; GTB6;
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR
2.0.50727; .NET CLR 1.1.4322; FDM; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
OfficeLiveConnector.1.4; OfficeLivePatch.1.3)', 0, 0, 0, 0, ...

> Apologies for raising as defect which does not look like it.

No problem. It's just easier if you ask a question in "Answers", and if we find a problem in there it's easy to convert the question over to a bug with all the information we need to address it.

I'll leave this open for now as Dan wanted to look at the field length of UserAgent on the log table.

> While I am a big fan of windows, I have to say they let me down this time :)

Well there's no accounting for taste. :D

> Thanks for your quick response. Any chance for a java client :)

If you want to write one then go for it. Unfortunately we lost 6 months of dev work waiting for JWebPane to be released. As far as I'm aware it still hasn't been - and we've put our efforts in elsewhere: http://wiki.xibo.org.uk/wiki/Install_Guide_Python_Client - That will eventually run on Linux, Mac and Windows.

Alex

Hi,

 I have the same problem. I'm surprised MS haven't already received a lot of negative feedback from website owners. They deserve it :-)

 Seeing as I'm only just playing with xibo so far, I've used MySQL workbench to change the column width;

ALTER TABLE `xibo`.`session` CHANGE COLUMN `UserAgent` `UserAgent` VARCHAR(510) NULL DEFAULT NULL ;

 I'll have to have a look through the code at some point :-)

Regards,

Keith

Hi Keith

Thanks for nudging us on this.

It's not been correctly tagged (myf fault) so its dropped of the radar.

What you've put in place is probably exactly what we'll end up doing. It just needs writing in to the 1.1.1 upgrade sql.

Cheers

Alex

Hi Alex,

 Thanks for the lightning response!

 I've only just run into this Xibo so "giving you nudge" was merely circumstantial ;-)

 As I just found out earlier today, the log table stores the user agent too so that'll need a bit of TLC too. Sheesh, MS have some interesting ideas with IE don't they?

 I found a few other glitches so I'm just off to check the 1.1.x branch and I'll bug them if they're still present. Nothing serious, just typos leading to the wrong variable name being used and things like that. Easy peasy fixes :-)

Have fun,

 Keith