r33lin

Problem Connecting to Auto Config Service

11 posts in this topic

Are you behind a corporate proxy?

Share this post


Link to post
Share on other sites

I am not behind a Proxy.

Is the IP that the client is trying to reach out to 165.227.29.181 on port 443 VIA SSL?  If so our Palo Alto Firewall is blocking it because it is categorized as unknown Traffic. 

Let me know and I can request that the category is changed and allowed by default. 

Share this post


Link to post
Share on other sites

I am not behind a Proxy.

Is the IP that the client is trying to reach out to 165.227.29.181 on port 443 VIA SSL?  If so our Palo Alto Firewall is blocking it because it is categorized as unknown Traffic. 

Let me know and I can request that the category is changed and allowed by default. 

Edit

I have added an exception on our firewall for the above IP and the application connected immediately.

But I still have no control of the client from the server. 

Server Logs

https://synergy-logs.symless.com/2017-11-02/9979-2017-11-02T10-02-04.log

Client Logs

https://synergy-logs.symless.com/2017-11-02/9979-2017-11-02T10-09-00.log

Edited by r33lin
spelling

Share this post


Link to post
Share on other sites

What OS is the client? This log line seems to be the issue:

[ Core    ] [2017-11-02T10:01:49] WARNING: secondary screen unavailable: unable to open screen
[ Core    ] [2017-11-02T10:01:49] DEBUG: retry in 60 seconds
[ Core    ] [2017-11-02T10:02:49] DEBUG: XOpenDisplay(":0.0")

Share this post


Link to post
Share on other sites
3 hours ago, r33lin said:

Ubuntu 16.04.3 LTS 64-Bit GNOME

We don't support that version of Ubuntu right now, but we'll be adding support soon.

Share this post


Link to post
Share on other sites

I have the same problem on Arch Linux.

Here are steps I did seems to be fixed it:

1. Remove ~/.Xauthority file. (Backup if it is needed for other app though)

2. Check use command xclock if app shows up, if not use xhost + to allow connection, this, I think, resolves the "XOpenDisplay" fail in Synergy

3. Restart X server (I just reboot)

Credit: https://www.linuxquestions.org/questions/linux-server-73/can't-open-display-no-protocol-specified-using-gdm-4175462031/

Share this post


Link to post
Share on other sites
15 minutes ago, Nick Bolton said:

Excellent workaround! I’m sure @Andrew Nelless will be interested in this!

Thank you.

However, switching server/client mode will cause Synergy core/service crash though. 

Not always, but sometimes. Next time it happens, I will upload the log.

Edited by Boyang

Share this post


Link to post
Share on other sites
2 minutes ago, Boyang said:

However, switching server/client mode will cause Synergy core/service crash though. 

Not always, but sometimes. Next time it happens, I will upload the log.

Thanks, that'd be awesome. We're working on service crash bugs this week.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now