Skip to content

Commit eaa791c

Browse files
committed
Improve wording
1 parent 4f02098 commit eaa791c

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This feature allows you to expose a specific TCP/UDP port on your private IPv6 i
1313
works by creating a forwarding rule on a public-facing Compute Resource Node (CRN) IPv4 address, which acts as a
1414
gateway.
1515

16-
Up to 20 internal port might be forwarded per instance.
16+
Up to 20 internal ports might be forwarded per instance.
1717

1818
## Requirements
1919

@@ -36,7 +36,10 @@ From there you will be able to show, add, modify and remove ports.
3636
![Close up of an added port](port-config-added.jpg)
3737

3838
After adding a port, the external port will be shown after a minute or so.
39+
When setup is complete, the port on the instance will be accessible using the CRN domain name or ip and the external port.
3940

41+
If a [custom domain name ](../custom-domains/setup.md) has been set up for your instance, it might also be used. To check
42+
if the custom domain was properly setup the dns should resolve to the hosting CRN ipv4 ip.
4043
## From the aleph CLI
4144

4245
Port forwarding for your instance can be managed via the `port-forwarder` subcommand group.

0 commit comments

Comments
 (0)