Restarting a Tunnel

If your Client machine has been rebooted, or your Docker runtime has been restarted, you can restart the tunnel from your Client by running the same command again, for example:

> aqueduct
╤╤ flood aqueduct ╤╤ : run
[√] Aqueduct client container already connected to tunnel UUID XMesS6L9G0Q

This will attempt to connect to the last known tunnel Server created by your Client.

You can also force a restart of the Client container with the --restart-container flag as follows:

> aqueduct --restart-container --target https://www.ecorp.dev
╤╤ flood aqueduct ╤╤ : run
Target mappings:
+-----------------------+-------------------+------+
| --TARGET | HOST:PORT | SSL? |
+-----------------------+-------------------+------+
| https://www.ecorp.dev | www.ecorp.dev:443 | true |
+-----------------------+-------------------+------+
==> Pulling tunnel client docker image
stable: Pulling from floodio/aqueduct
Digest: sha256:675b92a017ecd5be8c436ecb4659c6e5e117cf6e422a1b99e7b8ae5484b9d2e7
Status: Image is up to date for floodio/aqueduct:stable
==> Preparing tunnel
- Attempting to reuse tunnel with UUIDXMesS6L9G0Q
--> Tunnel UUID: XMesS6L9G0Q
- Waiting for tunnel server to start
[√] Tunnel started
- Querying tunnel name and DNS
- Copying tunnel certificates
==> Starting tunnel client
- Waiting for client to start
[√] Started aqueduct with container id: 6c71c6ff
==> Checking client container is up & stable for 10s
[√] Container is up

This is useful in situations where the Client needs to be refreshed, especially if DNS resolution has changed for some reason on your local networks as it applies to the target.