Expose solution

[AhmedHanafy725]

Which package/s are you suggesting this feature for?

Dashboard

Is your feature request related to a problem? Please describe

a user might have a server running on a local machine or vm on the grid and this machine has Mycelium IP or Yggdrasil and would like to expose this server to the public network.

Describe the solution you'd like

The user can use the grid gateways to expose his server on a domain by using his machine IP or the vm IP (can be Mycelium IP, Yggdrasil IP, or public IP (v4 or v6))

The solution should ask for the gateway node, a subdomain, the IP, and the port.

[maayarosama]

@ehab-hassan Please provide an icon for this solution

[maayarosama]

Issue Update Format

1. Work Completed: Added the expose solution to the dashboard
2. Work in Progress (WIP):
   • waiting on expose icon
   • adding docs to the manual
   • adding validation to the ip field

[ehab-hassan]

@ehab-hassan Please provide an icon for this solution

I like option2

[maayarosama]

1. Work Completed:

• added expose icon
• added docs to the manual
• added validation to the ip field

[maayarosama]

Issue Update Format

• Work Completed: Removed deploying vm
• Investigation and Solution: I get an error while deploying , still investigating

[AhmedHanafy725]

This means that you are trying to deploy a gateway workload and using a network's name doesn't exist (you didn't deploy it and you don't need it). This network field on the gateway workload is only used for wireguard network

[maayarosama]

• Work Completed: Fixed dialoge feature with domain
• Investigation and Solution: Deployment list doesn't work probably as there's no projectNae added to the gateway contract

[maayarosama]

Work Completed:

• Fixed dialogue feature on row-click
• Fixed rollbackGateway
• Fixed deleting domain instances

[A-Harby]

Devnet, 99b5130.

It worked on all networks except for IPv6, it gives me an error not found.

its missing the http://, could be the error.

[A-Harby]

Also, using wireguard is not supported; its deployment is different than the other networks.

[A-Harby]

Last thing what does the health mean?

Because it shows ok in either way the domain is up or down.

[maayarosama]

Also, using wireguard is not supported; its deployment is different than the other networks.

Wiregaurd is indeed not supported

[maayarosama]

Devnet, 99b5130.

It worked on all networks except for IPv6, it gives me an error not found.

its missing the http://, could be the error.

I think the ipv6 you provided isn't a valid ip, Please try it again because I tried and ipv6 works just fine

[A-Harby]

I think the ipv6 you provided isn't a valid ip, Please try it again because I tried and ipv6 works just fine

True, it wasn't with the IPv6 but rather with the tls passthrough option; if you turn it on, the domain will not work.

Also chip should be green and red, and in some deployment table is called status.

[maayarosama]

I think the ipv6 you provided isn't a valid ip, Please try it again because I tried and ipv6 works just fine

True, it wasn't with the IPv6 but rather with the tls passthrough option; if you turn it on, the domain will not work.

Also chip should be green and red, and in some deployment table is called status.

If the server doesn't have a certificate and you enable the tls passthrough it will never work

[A-Harby]

Verified, Devnet a948bfa.

The domain is now working fine with all network interfaces except for Wiregurad and with the TLS option on/off.

And health chip is fixed.

Test case: TC2827 - Deploy Domain