You can find a generic website setup tutorial in the Knowledgebase. The process for setting up protection for a website should be simple, requiring only at a minimum that you:
By not specifying a domain name in the port entry (HTTP) or if using any form of TCP port forwarding (no HTTP filtering) an unlimited number of domain names can be protected. If each domain (and subdomains) are set up as individual zones (such as for customized mitigation or caching) then they will be counted as individual ports and subject to port limits.
Any time that DNS changes are made, you need to wait for propagation to complete. Propagation can take up to 48 hours, however often requires much less.
The real IP of the connecting client is available in the X-Real-IP header.For more information including setup instructions see the Knowledgebase page.
There are two common causes of this:
Firstly, is this really what you want? FTP and SSH are typically privileged private services and should not be available on publicly accessible ports. To this effect, SSH over port 22 is currently restricted. If you require this, use a TCP DMZ entry, although we would instead recommend that instead a port other than 22 be used, FTP uses a large, and often dynamic port range for communication due to this we have a special port type of "FTP" to proxy this protocol.
If you are setting up your domain to use our DNS system then our nameservers are ns1.x4b.net and ns2.x4b.net.