Mike,
I really appreciate your help and quick response.
1.
My guess would be that guacd is already running. Since the wildcard address
> would result in guacd listening on all interfaces, that's guaranteed to
> conflict with any instance of guacd listening on any interface.
That is what I und
On Thu, Aug 3, 2017 at 6:54 PM, Mike Jumper wrote:
> On Thu, Aug 3, 2017 at 6:50 PM, James Fraser
> wrote:
>> Hi Nick
>>
>> Thanks for your response.
>>
>> After sending off this message I did some digging.
>>
>> I am using JDBC and LDAP auth together.
>>
>> I was digging around the Server Heap e
On Thu, Aug 3, 2017 at 6:50 PM, James Fraser
wrote:
> Hi Nick
>
> Thanks for your response.
>
> After sending off this message I did some digging.
>
> I am using JDBC and LDAP auth together.
>
> I was digging around the Server Heap error and think that you are on the
> right track with Xmx value.
Hi Nick
Thanks for your response.
After sending off this message I did some digging.
I am using JDBC and LDAP auth together.
I was digging around the Server Heap error and think that you are on the right
track with Xmx value.
It was out of the box (from apt-get) set to -Xmx128m, I have adjuste
Okay, let me try to take these one at a time...
On Thursday, August 3, 2017, 8:16:09 PM EDT, James Fraser
wrote:
> I recently upgraded to 0.9.13 and am experiencing an issue with my Production
> server.
> This is potentially a Tomcat issue or JDBC driver issue.
What extensions do you have
Hi All
I recently upgraded to 0.9.13 and am experiencing an issue with my Production
server.
This is potentially a Tomcat issue or JDBC driver issue.
If anyone can comment that would be great.
Looking at the Catalina.out file I found
WARNING: The web application [guacamole] appears to have sta
On Aug 3, 2017 03:54, "Amarjeet Singh" wrote:
...
Configuration in *guacamole.properties*
*# Hostname and port of guacamole proxy*
*guacd-hostname:172.15.9.56*
*guacd-port:4822*
*# Auth provider class (authenticates user/pass combination, needed if
using the provided login screen)*
* auth-prov
On Aug 3, 2017 06:38, "Nick Couchman" wrote:
Amarjeet,
I'm not sure why the 0.0.0.0 option does not work - I will have to dig into
that. Glad it is working for you, though.
My guess would be that guacd is already running. Since the wildcard address
would result in guacd listening on all inter
Amarjeet,
I'm not sure why the 0.0.0.0 option does not work - I will have to dig into
that. Glad it is working for you, though.
Do keep in mind that, in the configuration you have there, the Guacamole
Protocol traffic between the Guacamole Client instance and guacd will be
plaintext and reada
Nick,
I apologize for posting on both user and dev. I am new to this mailing
list. I was not sure whether to post on dev or user team.
I am really grateful to you. The above issue is resolved.
So, you'd want to start guacd like so:
> guacd -b 172.15.9.56
This above command worked and I am ab
Amarjeet,
First, please do not post to both Dev and User lists at the same time. It
causes confusion.
Second, your issue is likely that your guacd instance is listening *only* on
the loopback interface (127.0.0.1) on the Linux system and not on all
interfaces. This is denoted by the "127.0.0.
Hi Team,
I am working on Guacamole Client and Server. I did the following steps:-
AIM : To integrate Guacamole using a single URL which contains all the
information instead of usermapping.xml or noauth-config.xml files.
Installed Guacamole client, Tomcat, in Windows 10.
Installed Gucamole Serv
12 matches
Mail list logo
