Thanks, but we need to see the config file from within the container to make sure it's been updated accordingly.
When you see something like this:
failed to connect to ER[ziti-edge-router] [-3001/temporary failure]
it's might be internet related, but it's usually configuration related. wrong port in advertise section, hostname not eternal DNS in the advertise section etc.
Do you mean the ziti-edge-router.yaml in the router container?
v: 3
identity:
cert: "/persistent/ziti-edge-router.cert"
server_cert: "/persistent/ziti-edge-router.server.chain.cert"
key: "/persistent/ziti-edge-router.key"
ca: "/persistent/ziti-edge-router.cas"
#alt_server_certs:
ctrl:
endpoint: tls:controller.sdn.100fil.ca:6262
link:
dialers:
- binding: transport
listeners:
- binding: transport
bind: tls:0.0.0.0:10080
advertise: tls:ziti-edge-router:10080
options:
outQueueSize: 4
listeners:
edge:
csr:
country: US
province: NC
locality: Charlotte
organization: NetFoundry
organizationalUnit: Ziti
sans:
dns:
- localhost
- ziti-edge-router
- 6ef52822603b
ip:
- "127.0.0.1"
#transport:
#alt_server_certs:
forwarder:
latencyProbeInterval: 0
xgressDialQueueLength: 1000
xgressDialWorkerCount: 128
linkDialQueueLength: 1000
linkDialWorkerCount: 32
ziti@4387c0ddfa01:/persistent$
Did you use docker compose? If so, did you make sure to down -v? If you see advertise: ziti-edge-router:8442 (like you have shown), it won't work. You need to make sure that has the expected advertised address
ok i'll do the down -v 
You'll have to reenroll your tunneler too but before getting there, make sure the advertised address is correct for the controller and router. It's vital to the overall deployment. The controller seems to have the correct address so I'm thinking the down -v is the answer. You should have seen this log message when the router comes online telling you that it's not overwriting the existing config file:
echo " Found existing config file ${_CONFIG_PATH}, not creating a new config."
I believe that's why your config is incorrect.
How do i delete the identity in the linux tunneller? Is deleting the json and jwt is enough?
root@vi-conteneur-01:~# ziti-edge-tunnel delete vi-conteneur-01.json
received response <{"Success":false,"Error":"Identifier info is not found in the remove identity request","Data":{"Command":"RemoveIdentity","Data":{}},"Code":500}
root@vi-conteneur-01:~# ziti-edge-tunnel delete vi-conteneur-01
received response <{"Success":false,"Error":"Identifier info is not found in the remove identity request","Data":{"Command":"RemoveIdentity","Data":{}},"Code":500}
root@vi-conteneur-01:~# ziti-edge-tunnel dump
received response <{"Success":true,"Code":0}
root@vi-conteneur-01:~#
Delete the identity file from /opt/openziti/etc/ and restart the service.
Congrats! Enjoy your new overlay network!
Let's dive into BrowZer now!! 
I've not deployed browser with a docker compose deployed OpenZiti instance. The walkthrough video and example you can find here: Example Enabling BrowZer | OpenZiti
I'm certain it can work, but docker often brings a few differences that might need to be sorted out because of those nuances in docker.
Hi Clint,
Any chance you could post another youtube video explaining the RDP setup again as your sound cut out as you were explainging this in the video unfortunately ?
Cheers,
Colin
Hi @colin. Welcome to the community and to OpenZiti! Sure I can do that! I'll make a shorter, focused video demonstrating it. If not tonight then by the end of the week for sure.
@colin here you go -- walkthrough of using ZAC 3.1.0+ to make an RDP connection
Thanks for that Clint 
or two!! 
