Hello!
I have read through the Openziti.io site quite a lot the last weeks.
I really like that this is Open Source and seems to be a really cool thing.
In the past I used Twingate to access my Home Assistant Instance from external (my Android phone).
That worked fine but I want to have something now which I host myself and there Openziti seems to be perfect for such things.
Also I just installed a second RaspberryPi here running some Docker Container apps using Portainer.
Have also added now the Openziti Quickstart to my Portainer Templates file.
OK, so as I understand it in order to reach my Openziti Network from the Ziti Mobile Edge app on Android I need to open the TCP Ports 80 and 443 in my Router towards the IP address of my RaspberryPi where I install Openziti correct?
I have a duckdns address, so I assume I would need to add that to the Ziti Controller as
ZITI_CTRL_ADVERTISED_ADDRESS and ZITI_ROUTER_ADVERTISED_ADDRESS ??
Hi again!
I started again from scratch now and when doing the quickstart the openziti-ziti-controller-1 is not starting up.
In the log I see this now:
[ 0.848] INFO ziti/controller/server.NewController: edge controller instance id: cm9s367210000i9qpkdc3tjdd
[ 0.848] INFO ziti/controller/server.(*Controller).Initialize: initializing edge
[ 0.849] INFO ziti/controller/sync_strats.(*InstantStrategy).Initialize: {logSize=[10000] listenerBufferSizes=[1000]} initialized controller router data model
[ 0.852] INFO ziti/controller/sync_strats.(*InstantStrategy).BuildAll.func1: {index=[5]} initialized router data model from db
[ 0.852] INFO ziti/controller/internal/policy.NewSessionEnforcer: {sessionTimeout=[30m0s] frequency=[5s]} session enforcer configured
[ 0.853] FATAL ziti/controller/subcmd.NewEdgeInitializeCmd.func2: already initialized: Ziti Edge default admin already defined
--- There was an error while initializing the controller ---
Hi @Wishmasterflo, welcome to the community and to OpenZiti!
It's hard to know exactly for me. You need to forward at least one controller and at least one router port. Depending on how you configure your OpenZiti overlay, you may have 2-4 ports configured. This video references the older quickstarts, but the information is still largely valid. It describes those 4 ports. With ALPN configured (which you do by simply using the same port for the controller and router), there's only ports necessary.
Yes. When you first start, the process of bootstrapping your PKI is really important. Any addresses you will want advertise for OpenZiti components to connect to, must be specified. You can always fix this after the fact, and for one who's quite familiar with PKIs and setting them up, it's not hard but that's not "most people" usually... 
So if you get it wrong, at the beginning it's usually just easier to delete everything and start over (imo). Unless of course, you want to learn what's going on during the process. Just beware that getting your PKI setup, is a fickle process if you're not well-versed with PKIs. Hope that makes sense...
As for your second post, which "quickstart" are you using? Can you provide an exact set of steps you're performing?
Hi!
Thanks, and thank you for your answer.
I will take a look at that.
I used the Docker Compose Quickstart from here.
If the quickstart compose is failing, did you stop the controller and bring it back up? If you're starting from scratch, make sure you do a "docker compose down -v" first to remove any volumes. Seems like there's some leftover state that you probably want to remove.
That quickstart really is meant for local learning first and foremost. I think it's pretty great for that sort of use but if you're looking for a deployment to survive long-term, it's probably worthwhile to have a look at the "deployment" guides. We're currently trying to restructure these somewhat so the information / links might change. You can find those here: Deploying with Docker | OpenZiti
hth
Yes I tried to stop/start the Controller and it failed with the same error.
Also before I executed the quickstart steps I did a "docker compose down -v" .
I will check and do all this once again now.
It seems that something is left somewhere but I dont know how and where.
Let me check again now.
EDIT: OK now it worked. Strange, I did the same steps as before. Not sure what went wrong but now the controller and everything is up and running.