You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dashboard/ingress-rules.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,20 +22,22 @@ To add an ingress rule, click on **Add New** button. You will see a form like th
22
22

23
23
24
24
You can choose the protocol your application required.
25
-
-**HTTP**: Currently, only port 80 is supported.
25
+
-**HTTP**: You can choose any port for your application. It's recommended to use port 80 for HTTP.
26
26
-**HTTPS**: Currently, only port 443 is supported.
27
27
> Note: To enable, **HTTPS Redirection**, you will have to create a redirect rule. You can follow [**this docs**](/docs/dashboard/redirect-rules#https-redirect) section to create a redirect rule.
28
-
-**TCP**: If your application requires a custom port, you can choose this protocol.
29
-
> **NOTE : ** In case of TCP, You can't create more than one ingress rule with the same port. The domain will be ignored in this case, you can just put your server IP address in the domain field.
28
+
-**TCP**: If your application relies on TCP protocol, you can choose this option. You can choose any port for your application.
29
+
> NOTE : In case of TCP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
30
+
-**UDP**: If your application relies on UDP protocol, you can choose this option. You can choose any port for your application.
31
+
> NOTE : In case of UDP, You don't need any domain. You can directly connect your application to your server's IP and port (you choose).
30
32
31
33
Then, you can choose the domain you want to connect to your application. If you don't have any domain, you can add it in [**Domains**](/docs/dashboard/domains) section.
32
34
33
-
Finally, you can choose the application you want to connect to your domain. If you don't have any application, you can deploy one by following [**this docs**](/docs/dashboard/deploy_new_application) section.
35
+
**Finally**, you can choose the application you want to connect to your domain. If you don't have any application, you can deploy one by following [**this docs**](/docs/dashboard/deploy_new_application) section.
34
36
35
37
Hurrah! You have successfully created an ingress rule. Now, you can access your application via your domain.
36
38
It takes upto 1 minute to apply the changes.
37
39
38
-
> **Note :** If you have created an TCP ingress rule, you will have to manually open the port in your server's firewall (if you have any). Also, during apply the changes, you may face a downtime of ~10 seconds.
40
+
> **Note :** If you have created an ingress rule for port except 80 and 443, you will have to wait for upto ~30 seconds to apply the changes. This is because, we have to reload HAProxy or UDPProxy and other services to expose the port. You should open the port in your server's firewall too.
39
41
40
42
### Delete Ingress Rule
41
43
To delete an ingress rule, click on **Delete** button. You will see a confirmation dialog. Confirm it and your ingress rule will be deleted.
0 commit comments