From 4f0209899f20fa21e082775648f99f4d175b0399 Mon Sep 17 00:00:00 2001 From: Olivier Le Thanh Duong Date: Thu, 26 Jun 2025 17:03:15 +0200 Subject: [PATCH 1/2] Fix link --- docs/.vitepress/config.mts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/.vitepress/config.mts b/docs/.vitepress/config.mts index fc0a5c3..e69ef7b 100644 --- a/docs/.vitepress/config.mts +++ b/docs/.vitepress/config.mts @@ -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' }, ] }, { From eaa791c58031452bb4f90e623362fbb4511aea46 Mon Sep 17 00:00:00 2001 From: Olivier Le Thanh Duong Date: Thu, 26 Jun 2025 17:04:42 +0200 Subject: [PATCH 2/2] Improve wording --- .../deploying-and-hosting/ipv4/ipv4-port-forwarding.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding.md b/docs/devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding.md index a256cad..08e20a1 100644 --- a/docs/devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding.md +++ b/docs/devhub/deploying-and-hosting/ipv4/ipv4-port-forwarding.md @@ -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 @@ -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.