On 11/10/2017 06:36 PM, Mihai Moldovan wrote: > HA! I was finally able to reproduce your issue locally! > > In a Fedora 26 VM, I set the hostname as follows: > > hostnamectl set-hostname fedora.local.home.ionic.de > > Then, I edited /etc/hosts and added: > > 192.168.122.128 fedora fedora.local.home.ionic.de > > This leads to exactly the problem you described. > > > If I change "fedora" to resolve to 127.0.0.1 instead (with > fedora.local.home.ionic.de staying on 192.168.122.128), I can connect via X2Go > again. > > Can you confirm this?
Weirdly, this seems not to happen if the hostname is *not* set to a FQDN. I have a machine that is working flawlessly with such a setup: hostname: shortname /etc/hosts: shortname or FQDN not set dns: returning public IPv4 and IPv6 addresses for FQDN; shortname will be extended to FQDN automatically (and hence also resolves to these public addresses) In this scenario, connecting via X2Go works just fine, even though neither address is 127.0.0.1. This, incidentally, is also the recommended setup on Debian-based systems, whereas Red Hat recommends using the FQDN as the host name. I'll have to find out why a FQDN hostname leads to such problems... and why the heck everything works fine iff the shortname is mapped to 127.0.0.1. Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev