Members of the Fleet,

We have made some changes to several security related account settings, as well as how IP connections are handled at Nebulance. However, IP information can be wrong for many reasons. IP's are sold and moved between companies, or within a company, and it may take some time for the type of connection and country of use to be updated in the databases. It was always possible that your connection would not be recognized properly and you could have had difficulties accessing the site.

As per our previous announcement, and in an attempt to remedy the above issue, we have decided to modify some of our security and connection related rules for browsing the site. Please take a look at the following list of updates, and make any necessary changes to your account accordingly. VPN, Proxy, and Hosting IPs will be defined as 'Restricted IPs' for the duration of this post. Please also note that most seedboxes will return as proxies/hosting IPs whether shared or dedicated.

Seeding IPs are still unrestricted so long as they are not Tor. You may seed from up to three (3) concurrent IP addresses, regardless of what or where they are, with the single exception of Tor.

Browsing the website from an IP address that is returned as a 'Restricted IP' from our API partner, will require the account to have 2FA enabled. No further whitelisting will be necessary, and there will no longer be a process to support browsing from a 'Restricted IP' without having 2FA enabled moving forward.

Accessing the NBL API via an IP address that is returned a 'Restricted IP' from our API partner, will require the account to have 2FA enabled, otherwise the connection will be 403'd. We will no longer require the static IP of your seedbox to be whitelisted, or sent in a Staff PM, only that your account has 2FA enabled.

2FA can now only be set/removed/modified for an account that is connecting from its 'Home IP' country code, the options have been removed from a user's profile entirely, if the connection is detected as a 'Restricted IP' address, or a 'non-Restricted IP' whose country code does not match your Home Country. You may Contact Staff for an override if necessary, but these will be given at staff's discretion on a case by case basis.

A user's email address may only be changed on an account that is connecting from its 'Home IP' country code. You may Contact Staff for an override if necessary, but these will be given at staff's discretion on a case by case basis.

API keys may only be created or modified on an account that is connecting from its 'Home IP' country code. You may Contact Staff for an override if necessary, but these will be given at staff's discretion on a case by case basis.

Traveling outside of your home country still needs to be approved by way of a Staff PM indicating where you are traveling to, and how long you will be there, under most circumstances. If you plan to connect to NBL via a non restricted IP address from a different country code than your Home Country, then it is recommended you have 2FA enabled prior to, and use a VPN throughout the duration of your trip. You will not be able to set 2FA once you leave your recorded Home Country. If this is not an option for you, then you can still submit a Staff PM and we will work with the user on a case by case basis.

Cloudflare and other iCloud Relays are no longer blacklisted so long as the account has 2FA Enabled.

Free VPN providers are still discouraged from use for various reasons related to restrictions by the VPN Provider. Please Note this no longer means banned, but your results may vary relating to the quality of the connection. Staff will not be able to assist with any issues related to the use of a free VPN provider.

While we have tested these new systems extensively in a development environment, there is no amount of testing all scenarios that will replicate the live use of them. In the event you believe an IP address was detected in error, we would ask that you submit a Staff PM, or visit us in IRC in the #nbl-help channel.

These rules are in effect as of the time of this posting, but may not be fully enforced until September 1st, 2024 in order to give users ample time to make the appropriate changes to their accounts to be in compliance. When these rules are fully enforced, as opposed to system notifications, and the possible banning of the account for rule violations, connections with 'Restricted IP's, or invalid Country Codes, will simply be rejected entirely from the site should the account not have 2FA enabled.

// So say we all