Try our conversational search powered by Generative AI!
AI OnAI Off
How to solve the Licesense Exception: is not a valid ip-address
Vote:
Download a license based on the ip address, but got the error: LicenseException: ???? is not a valid ip-address.
Sep 18, 2008 14:14
Hi Hua,
What IP did you bind the license to?
Could you paste your ipconfig /all?
Pretty much any IP can be used that's not a loopback ip.
Sep 18, 2008 16:32
Click start -> run -> enter "cmd" -> click "ok" -> enter "ipconfig /all" in the command window and click enter -> paste the result here
#23947
Sep 19, 2008 0:12
I would recommend binding the license to a MAC address since its static, while the IP address can change.
#23958
Sep 19, 2008 8:35
Go to http://checkip.dyndns.org/ to check what IP address you are identified with outside your local network.
#25681
Oct 30, 2008 20:18
Hi, this seems like a similar issue tot eh on e I am receiving. I have an external IP which is assigned via NAT. The scheduled services seem to run as the servers local IP and as such fail to run as the local IP is not the external IP that the license is bound to. Is there a way to resolve this?
Oct 15, 2010 10:05
You should bind the license to the internal ip. It needs to be bound to something that the EPiServer code can find (local adapters only). For servers, using MAC or IP of a local adapter is pretty much the same. If you need to replace the adapter or machine due to hardware failure, the IP address can be re-used by new hardware, but the MAC is adapter specific. But most adapters allow you to change the MAC address too, so it is really does not matter.
Oct 15, 2010 12:26
Sam Brooks
- Dec 09, 2019 18:12
Thanks! i had an this issue because i was using the external ip address instead of my internal ip address. Your explanation helped me to understand why this wasn't working.
I had the same problem, but solved it when I found out that someone changed the licenseFilePath= in episerver.config to the site root, which had an outdated license.config file
Nov 10, 2011 6:40
Hi,
I am having the same problem. I ahve generated the license with Public IP address: 54.83.148.10 and I started getting error "54.83.148.10 is not a valid ip-address"
I ahve pasted my ipconfig /all result from the server end. Please have a look into the same and suggest for the solution.
=================================================================
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : WIN-LDE76FN4GOF
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : us-east-1.ec2-utilities.amazonaws.com
ec2-utilities.amazonaws.com
ec2.internal
compute-1.internal
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82599 Virtual Function
Physical Address. . . . . . . . . : 0E-5B-20-46-02-39
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::551b:2a7:19d6:6f5c%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.165(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Lease Obtained. . . . . . . . . . : Monday, January 16, 2017 4:53:28 AM
Lease Expires . . . . . . . . . . : Friday, March 31, 2017 3:25:00 AM
Default Gateway . . . . . . . . . : 10.0.0.129
DHCP Server . . . . . . . . . . . : 10.0.0.129
DHCPv6 IAID . . . . . . . . . . . : 353262368
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-0E-42-60-0E-5B-20-46-02-39
DNS Servers . . . . . . . . . . . : 10.0.0.2
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{C83848F4-EB53-4646-9D02-28BDF7FCE89C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:85:1c7e:c9ac:6bf5(Prefer
red)
Link-local IPv6 Address . . . . . : fe80::85:1c7e:c9ac:6bf5%12(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 385875968
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-0E-42-60-0E-5B-20-46-02-39
NetBIOS over Tcpip. . . . . . . . : Disabled
=========================================================
Regards
Cara
Mar 31, 2017 8:46
If I am not misstaken I think it will read the internal Ip (IPv4 Address. . . . . . . . . . . : 10.0.0.165(Preferred))
As said earlier in this thread, it is better to bind on MAC since that will not change.
Mar 31, 2017 9:26
MAC adress is the this one above
Physical Address. . . . . . . . . : 0E-5B-20-46-02-39
Mar 31, 2017 10:15
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
