This article applies to NetFoundry networks version 6 or lower. Refer to Finding Your Network Version for detailed information on determining your Network Version.

Common Registration Errors

Registration keys can be used exactly once until they expire, which is typically 24 hours after creation. If the key is expired simply recreate the endpoint, gateway, or edge router.

This troubleshooting guide assumes you've already attempted registration. If not you may go back to manual registration instructions for the Cloud Gateway VM.

Issue #1: Registration Key Invalid

If you examine the system log, and see an error that the Registration Key is invalid, you may have mis-entered the Registration Key into the User Data Field when you created the Gateway Instance in Step 4 above.

Resolution: Terminate the gateway EC2 instance and try again, paying particular attention to what you enter into the User Data Field.

[41.924131] cloud-init[1129]: November 16 19:31:53 Ensuring nf services are not running
[41.929536] cloud-init[1129]: November 16 19:31:53 url:
[41.940879] cloud-init[1129]: ('', '{"key": "55CF73C9B5F71EC152A49A1F7885F04E62881482"}')
[41.948008] cloud-init[1129]: November 16 19:31:54 status code: 500
[41.952557] cloud-init[1129]: November 16 19:31:54 content: {"timestamp":1510860714660,"status":500,"error":"Internal Server Error","exception":"java.lang.IllegalArgumentException","message":"Registration key 55CF73C9B5F71EC152A49A1F7885F04E62881482 invalid.","path":"/registration/key"}
[41.964972] cloud-init[1129]: November 16 19:31:54 NFN Registration Error received status code 500

Issue #2: NetFoundry Registration Error Connection Timed Out

Gateway Endpoints need outbound connectivity from a VPC by way of either an Internet Gateway (IGW), or a NAT Gateway. Amazon refers to subnets with connectivity through an IGW as "public subnets". Those that are connected via a NAT Gateway are considered "private subnets". Most times, issues with gateways not registering have to do with its ability to reach Internet hosts.

If you examine the system log, and see an error that registration timed out, the likely cause is that the EC2 instance has no outbound connectivity to the Internet.

Resolution: Terminate the gateway EC2 instance, and re-create it on a subnet with outbound connectivity to the Internet.

[48.856275] cloud-init[1129]: November 16 20:10:00 Ensuring nf services are not running
[48.859887] cloud-init[1129]: November 16 20:10:00 url:
[48.863658] cloud-init[1129]: ('', '{"key": "55CF73C9B5F71EC152A49A1F7885F04E62881482"}')
[48.873223] cloud-init[1129]: November 16 20:10:20 NFN Registration Error Connection Timed Out


Where to find registration logs for the AWS Cloud Gateway

If a gateway fails to register with the NetFoundry Console, the system log may provide a clue as to the issue. To view the system log of an instance from the EC2 Dashboard, click on the instance row, and select Instance Settings → Get System Log from the Actions menu.


A system log dialog will appear on screen. Scroll to the bottom and locate the output from the cloud-init process.


Was this article helpful?
0 out of 3 found this helpful



Article is closed for comments.