Hi,
I'm using SOS 4.1. My SOS Server has dynamic IP address, so I'm using the dynamic DNS service from www.no-ip.info. Then on SOS server, I created a user key, specifying server address as xxx.no-ip.info
When I looked at the key file generated, I saw the second line written as:
Server:xxx
Thinking this mismatch is by-design, I ignored it and imported the key file into SOS client. The key was imported successfully. But when I tried to connect to server, it threw an error message: "Invalid Encryption Key."
Am I missing some step ?
Thanks in advance.
Dotnetjunky
Invalid Encryption Key
Moderator: SourceGear
The key file often contains just a portion of the servername string used to create the key.
Generally the invalid encryption key error is because there's a mismatch in the server name/IP used to create the key and the server name/IP used to connect with.
One thing to check is if there is an invisible trailing space in the connection string.
Also, could the .iky or .key file have been modified somehow?
Generally the invalid encryption key error is because there's a mismatch in the server name/IP used to create the key and the server name/IP used to connect with.
One thing to check is if there is an invisible trailing space in the connection string.
Also, could the .iky or .key file have been modified somehow?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Same Issue
I had this same issue...
SOS Server generated the iky file but the IP address was of the local server and we were trying to connect via our public ip.
I modified the iky with the public IP address and imported into the client and I was connected.
SOS Server generated the iky file but the IP address was of the local server and we were trying to connect via our public ip.
I modified the iky with the public IP address and imported into the client and I was connected.