Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/.vitepress/config.mts
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ export default defineConfig({
items: [
{ text: 'Custom Domains', link: '/devhub/deploying-and-hosting/custom-domains/setup' },
{ text: 'Web Hosting', link: '/devhub/deploying-and-hosting/web-hosting/' },
{ text: 'Ipv4 Port fowarding', link: '/devhub/deploying-and-hosting/ipv4/ipv4-port-fowarding/' },
{ text: 'Ipv4 Port forwarding', link: 'devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding' },
]
},
{
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This feature allows you to expose a specific TCP/UDP port on your private IPv6 i
works by creating a forwarding rule on a public-facing Compute Resource Node (CRN) IPv4 address, which acts as a
gateway.

Up to 20 internal port might be forwarded per instance.
Up to 20 internal ports might be forwarded per instance.

## Requirements

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

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

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

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