[Thinlinc-technical] html5 again

[Arie Kruiniger]

Thanks, sorry didn't realise it was the OS logon not TL logon, should
have really.

Okay, so I have reached a point where the HTML5 client works on
Iceweasel. So it's clearly up and running on the network.

At this point I should probably 'fess up that I am trying to access
the HTML5 client via my Raspberry Pi. I am using a program called
Minimal Kiosk Browser. To my limited understanding, this works by
opening HTML5 tags with omxplayer, and this has worked for video
websites.

I realise I have no right to expect that this will actually work with
ThinLinc, especially as HTML5 client is not yet a supported feature.
But hey, this could be fun, so lets have a crack at it :)

As it stands, when I log on the pi gives me a webpage with the
thinlinc symbol, and two icons which say 'clipboard' and 'disconnect'.
Neither of the icons are responsive. Minimal Kiosk Browser has a
'play' button which ordinarily launches the html5 elements of the page
via omxplayer, but when I launch it, nothing happens.

I suppose you all hit a dead end with the TL client program for Raspberry Pi?

On 3 November 2013 22:30, Rob Evans <rob.evans at originvs.com> wrote:
> Sorry try running /opt/thinlinc/bin/tl-setup, from there you can change the password for web admin.
>
> Cheers
>
> Rob
>
>
> Rob Evans
>
> Partner
> Origin Virtual Solutions
>
> M: +44 (0)7717 780648
> E: rob.evans at originvs.com
> W: www.originvs.com
> Skype: originvs
>
> ________________________________________
> From: Arie Kruiniger [akruiniger at gmail.com]
> Sent: 03 November 2013 21:53
> To: Rob Evans
> Subject: Re: [Thinlinc-technical] html5 again
>
> Thank you for that, I can connect using the IP address.
>
> Next problem, it's not letting me sign in with admin/admin, as it does
> to the Web Administrator.
>
> How do I create a new user/allow an existing one to login?
>
> Thanks again.
>
> On 3 November 2013 21:45, Rob Evans <rob.evans at originvs.com> wrote:
>>
>>
>> Hi Arie,
>>
>> Have you opened a port forward in your router if it's doing NAT?
>>
>> Can you connect internally to apache? E.g. https://192.168.1.20:300
>>
>> If not your web server may not be running with SSL, did you install a self
>> signed or public certificate?
>>
>> Let me know cheers, Rob
>>
>>
>> Sent from Samsung tablet
>>
>> Arie Kruiniger <akruiniger at gmail.com> wrote:
>> Sorry to be a pain, but how do I know what address to navigate on the
>> browser on the client side?
>>
>> Is it always https://server.example.com:300/? Because that doesn't work for
>> me.
>>
>> I have opened that port in the router. Are there more settings I need
>> to configure before I get there?
>>
>> Sorry, I feel a bit clueless when confronted with all the settings in
>> the Web Administrator :/
>> _______________________________________________
>> Thinlinc-technical mailing list
>> Thinlinc-technical at lists.cendio.se
>> Manage your subscription:
>> http://lists.cendio.se/mailman/listinfo/thinlinc-technical
>>
>>
>>
>
>
>
>