Before starting to use the Filter, it is necessary to register your own IP on your Dashboard.
To do this, the DDNS (Dynamic DNS) service is available and present on any  router/firewall.
To configure the Dynamic DNS on your router click here.
If your router is not included in the list, visit the generic guide here.

Tips for the configuration:
» Check if a dynamic network (related to the desired username) is present in the Dashboard (Network Menu).

» Enter the username and password without copying and pasting in order to avoid possible errors (ex: unwanted blank spaces).

» Sometime the router might show an error, but the service is working properly.
Check that the network status is green and display your public IP (Network Menu).

» If the router doesn't allow the use of a custom Dynamic DNS, select "dyndns.org or dyndns.com" from the list and read the guide here. Be sure the router's WAN DNS settings point to: 185.236.104.104 and 185.236.105.105.

NOTE: Change your internal LAN's DNS settings only after a successful router synchronization.

» Check there are no automatic DNS redirection (port 53 tcp/udp) to thirdy party DNS provider (ex. to the ISP DNS servers) and, in case, ask to your ISP.

» Access your router DNS resolution tool (if present) and enter "members.dyndns.org". The proper reply should be: "185.236.104.104"

If the issue has not been resolved, please open a support ticket by clicking here.

To be able to use our service, you need to register your public IP (or public IPs) on your own Cloud Panel.
Below is some advice that may help you if you are unable to navigate:

» if you are using a Load-Balancer system (or backup line), it is necessary to add all public IPs on your Cloud Panel.

» Check the router/firewall and verify that there are no filters on 53 (DNS) port, which could block traffic to our ip classes (185.236.104.0/24 and 185.236.105.0/24).

» Check that our DNS ( Primary: 185,236.104.104, Secondary: 185.236.105.105) are reachable from your own network using a tool like a ping/tracer.
If they aren't reachable, send the tracer results (for both IP) to support@flashstart.com.

» Verify that the public IP (or public IPs) registered on the cloud is actually in use. You can see your own public IP through the following link what's my IP .

» Verify that on the router/firewall there are no blocking rules on the DNS resolution.
To test it, it's possible to use a different port instead of the standard one (53). 
Through the following commands we could check if blocking rules are present on the DNS resolution.
Then, open the cmd on your own device and run this commands:
-nslookup
-set port=53535
-blocked_domain ( where blocked_domain is a domain that should be blocked )
if the result is 185.236.107.107 it means that the domain has been filtered, then there is a redirection on port 53.

» Verify that you have properly/correctly configured the DNS on your device ( or through the DHCP service).

» If you configure our DNS on the router, it does not mean that internally the devices will use those DNS, so it's necessary to configure a DHCP service or firewall rules to force the use of our DNS also on the internal network. 

» Verify that your own public IP is registered on the system (network menu).

» Check that filter the license has not expired. You can check the expiry date on the Cloud Panel.

If the issue has not been resolved, please open a support ticket by clicking here.

If you’ve already unlocked the domain from your dashboard, changes could take some time before they take effect. Therefore, we suggest you wait for a few minutes, clear the cache of your Browser and try again to open the desired website.

if the problem persists below some actions that might help you solve it:

» Verify that the domain is not blocked, neither for the system category nor for geoblocking.
To do that, use the Search in lists tool from your panel. 
If it is blocked, it is necessary to add it to the Personal Whitelist in the Protection page.

» Try to resolve the domain using nslookup (cmd) through the following commands:
-nslookup yourdomain
for example to solve amazon.com the command will be:
nslookup amazon.com
NOTE: enter only the domain, without http/https.
If the command returns 185.236.107.107 it means that the domain is filtered, so add the domain to the Personal Whitelist .
If you see “Non-existent Domain” or “DNS request timed out”, please open a support ticket .

» Try to add the domain to the Personal Whitelist to unlock also potential CDNS as well as the connected domains (e.g. alias or third-level domains). 
Wait a few minutes, clear the Browser cache and try accessing the site again.

» Check the traffic log using the following tools, both of them are located inside the search menus:
Historical data: all traffic by day and time slot
Real time analysis: last minutes real time traffic 
Both tools allow you to view visited domains and specify whether or not they have been blocked by filters.

» Through Browser Advanced tools (e.g. on Chrome go to More tools -> Developer tools -> Network), it is possible to view all the domains that the site needs in order to load the different resources.  
If there are any blocked domains (in red), add them to the Personal Whitelist.

If the issue has not been resolved, please open a support ticket by clicking here.

In order for filters to be applied correctly on your network, you must first configure our DNS correctly within your network.
To do this there are several methods, such as manually configuring DNS on devices, using a dhcp service, using firewall rules, etc.
Here are some tips that might help you when setting filters:

» If you configure our DNS on the router, it does not mean that internally the devices will use that DNS, so it's necessary to configure a DHCP service or firewall rules to force the use of our DNS also on the internal network. 

» Verify that the protection rules have been correctly set up on the Cloud panel (Protection menu).

» Check that in the pc or in your own device there are no active VPNs, if so Turn off any VPNs present on your device, and try to access the blocked sites again.

» Verify that on the router/firewall there are no blocking rules on the DNS resolution.
Test if it's possible to use a different port instead of the standard one (53). 
Through the following commands, you can check if there exist blocking rules on the DNS resolution.
Open then the cmd on your own device and run this commands:
-nslookup
-set port=53535
-blocked_domain ( where blocked_domain is a domain that should be blocked )
If the result is 185.236.107.107 it means that the domain has been filtered, then there is a redirection to port 53.
In this case it’s necessary to disable redirection rules to the router/firewall.

If the issue has not been resolved, please open a support ticket by clicking here.

That message appears since you are trying to open a blocked website, using a HTTPS secure connection.
So the Browser informs you that the certificate has not been realeased by a reliable/recognized authority.

It's possible to avoid this error by installing our Certification Authority on your internal devices.
Here below the guide:
CA installation guide

Alternately, in most cases, you can click Proceed anyway to force the site to open.
In this case you will see the Filter blocked page.

The number of allowed networks depends on the number of licenses assigned to the customer.
There are two different possibilities:

» Site with different internet networks: in this case it is necessary to open a support ticket (see at the bottom of the page).

» Customer with different sites: you will need to assign a license for each site.
Ex: suppose we have a company structured in the following way:
     -Site A: 100 employees.
     -Site B: 10 employees.
     -Site C: 5 employees.
To filter all the sites it will be necessary to assign three different licenses to the same customer, respectively of 100, 10 and 5 nominal users (all the people that work inside the company).

NOTE: if a single license has already been granted for the sum of the users of the various locations, open a support ticket to manage the issue.

If the issue has not been resolved, please open a support ticket by clicking here.

You can change your own email, or that of a customer through the Dashboard.
Here are the two cases:

» Change your own account email.

» Change customer account email. 

NOTE: When the mail change occurs if there is a dynamic network synchronized via router you must also change the mail on the router (Dynamic DNS)

If the issue has not been resolved, please open a support ticket by clicking here.

Yes, you can do it using the Multiprofile advanced feature.
First of all, please read our Multiprofile guide.

Then, if you assign different pairs of DNSs (for example 185.236.104.104-185.236.105.105, 185.236.104.114-185.236.105.115 etc...), you will be able to create different filtering groups.

NOTE: This feature is possible either in the WORKGROUP area or in Windows Active Directory, but in this last case you will have to use advanced features, which are only active on proplus licenses. 
Check the guide for more information.


Mikrotik case

To simplify the configuration of the Mikrotik multi-profile, we have created a dedicated guide.

If the issue has not been resolved, please open a support ticket by clicking here.

Yes, our system allows you to customize the lock page by allowing you to change your logo, text, image that will appear on the screen etc.
In order to modify the block page, you need to click on the toolbar available on the top right side of the cloud panel (wrench symbol).
For further information about how to modify the block page click here.

Potential issues:

» If the block page does not open and the browser shows an error message, it could be because the package does not reach the destination host and so there might be a routing problem. 
In order to understand whether this is the cause of the problem, open the command prompt (cmd) and execute the following command: 
-tracert 185.236.107.107 
Shall there be any problems, open a ticket with our support center and send the result of the tracer. 

» When you upload images for the block page, make sure you have correctly respected the maximum dimensions and the formats allowed. 

» Moreover, the system allows you to customize the block page individually for each profile created on the account. 
However, in case you have a multiprofile network, the block page that will appear will always be the one associated with the default profile. 

» Shall a block message appear on the browser, make sure there are no third-party filters active online. In case you find some, we suggest you disable these filters so as to avoid any conflicts among the filters.

If the issue has not been resolved, please open a support ticket by clicking here.

You can gain access to the dashboard panel through this link, which is compatible with all types of browsers.

Potential issues:

» Try to input the password manually, without using copy and paste, so as to avoid including any special characters (e.g.: spaces). 

» If multiple languages are installed on the pc, check that the set one is the same as the keyboard one (on windows systems you can usually see this on the bottom right). 

» Check/Verify that the access email (username) is the one that has been used when registering to the service.

» Try to reset the password by clicking here.
IMPORTANT: if the ddns service for the synchronization of the public ip has already been configured, you will have to update the password on the router/firewall. 

» In case multiple sessions have been opened, the login might fail. 
Try to close the browser and access again. 

» If the access email or password has just been modified, wait for some minutes and try again.

If the issue has not been resolved, please open a support ticket by clicking here.