Requirements

Mobile phone requirements

The mobile phone must have internet access to receive Push Notifications.


If you have a firewall to restrict traffic to or from the Internet, you need to configure it to allow mobile devices to connect with Firebase Cloud Messaging (Push service) for devices on your network to receive messages.

 
Ports to open for incoming messages: 

  • 5228 
  • 5229 
  • 5230 
  • 443 

 

For outgoing connections, FCM does not provide specific IPs because their IP range changes too frequently, and your firewall rules could get out of date impacting your users' experience. Ideally, you will whitelist ports 5228-5230 with no IP restrictions. However, if you must have an IP restriction, you should whitelist all of the IP addresses in the IPv4 and IPv6 blocks listed in Google's ASN of 15169. This is a large list, and you should plan to update your rules monthly. Problems caused by firewall IP restrictions are often intermittent and difficult to diagnose. 


Choose one of these IP configurations to allow outgoing connections (option #1 is preferred): 

  • No IP restrictions 
  • All IP addresses contained in the IP blocks listed in Google's ASN of 15169. Do not forget to update this at least once a month. 

 

For more information about Firebase Cloud Messaging, see About FCM messages.

server installation requirements

hardware requirements for virtual machine

 These hardware requirements are provided for running one instance. Resources will need to increase as the load on the instance.
  • CPU: 4 cores or higher 
  • RAM: 4 GB or more 
  • HDD: at least 40 GB of free space

NETWORK REQUIREMENTS

Assign a public IP address or set up port forwarding or proxy ports to the Virtual Machine where the NoPass™ application server will be launched.

 

NoPass™ server requirements

The NoPass™  server needs Internet access to communicate with third-party services. If you have a firewall to restrict traffic to or from the Internet, you need to open the following ports: 


For incoming connections, whitelist the following default ports: 

  • 443 (HTTPS) 
  • 1812 (RADIUS authentication) 
  • 1813 (RADIUS accounting) 

For outgoing connections, whitelist the following ports: 

  • 53 (DNS) 
  • 80 (HTTP) 
  • 443 (HTTPS) 
  • 25,465 or 587 (SMTP) 
  • 1812 (RADIUS authentication) 
  • 1813 (RADIUS accounting) 

 

To use other ports for these protocols, open them.

 

LOCALHOST (VM) REQUIREMENTS

You can use various operating systems for the application that supports Docker installation. We recommend using the Ubuntu Server, which is a variant of the standard Ubuntu that is tailored for networks and services, bringing along high technical stability.


Install a Linux (or Windows) machine which will be used as a platform to run the NoPass™ Docker Image. (We recommend Linux Ubuntu 20.04).


NoPass Local Host Firewall:


To allow NoPass™ to communicate with the internet, you must open or forward ports specific to the environment you plan on using.

  • Port 80 http
  • Port 443 https
  • 53 *if doing DNS from console*

 

If you need RADIUS MFA:

  • Ports 1812 & 1813

 

Database Local Host Firewall:

If using an external database, you will need to forward the database port on your DB localhost to the NoPass™ server IP.

Forward the selected port to your NoPass™ server:

  • MySql - default port 3306
  • MsSql server - default port 1433
  • PostgreSQL - default port 5432

 

next topic: Configuration files

previous topic: Licensing

 

 

 

 

 

 

 

 

 

 

 

Suggest edits