When trying to connect to the server running the vsmserver I always get the error message “Server refused the connection. Is this a ThinLinc server?”.
I can connect to the server via ssh without a problem. systemctl status vsmserver.service also shows, that the vsmserver is active and running.
Even weirder are the logs, here the last entrys of /var/log/vsmserver.log:
2021-06-21 06:48:09 INFO vsmserver.session: User with uid 1002 requested a reconnection to 127.0.0.1:10
2021-06-21 06:48:09 INFO vsmserver: Verifying session 127.0.0.1:10 for <username>
2021-06-21 06:48:09 INFO vsmserver: Session 127.0.0.1:10 for <username> is alive and ready for reconnection
This means I am able to connect?
One other thing I noticed is, that the public hostname of the vsmagent as stated in /var/log/vsmagent.log is the same one as the inet address when running ifconfig. Could this be the reason? See the vsmagent.log:
2021-06-21 06:26:10 INFO vsmagent: VSM Agent version 4.12.1 build 6733 started
2021-06-21 06:26:10 INFO vsmagent: My public hostname is 192.168.155.58
and the return value of ifconfig | grep 192.168.155.58:
inet 192.168.155.58 netmask …
After all the troubleshooting doc states that a possible reason could be, that I’m trying to connect to the agent directly instead of the master. From B.2. Troubleshooting Specific Problems :
A user entering the wrong hostname, for example the hostname of one of the VSM agents, would also get this error message. Check that the user has entered the correct hostname. In very rare cases, this could also be caused by incorrect DNS data.
Is there any way to make the vsmagent use another ip address? Or could there be another reason for this error?
The problem was, that the server runs on a VM and as the agent uses the standard ip address of the master it wasn’t accessible from the outside. By editing the /opt/thinlinc/etc/conf.d/vsmagent.hconf file and writing agent_hostname=<my url> the agent is now accessible by the client.