@TheLumberjack After adding it, the BrowZer logs are as follows:
Ok. Did you read the error message? It seems pretty clear as to what failed, right?
Yes, I did check it, and my Ziti controller is functioning properly.
Can you issue a curl from the machine browzer runs on and verify it connects?
curl https://ctrl.openziti.devops.authing-inc.co:8441
Are there any other logs before that one that might be helpful? Is it restarting over and over ?
@TheLumberjack I finally succeeded, and I’m really happy. Thank you so much for your help! Additionally, I have a question regarding the configuration of intercept_address and intercept_port in the screenshot below. The setting ${ZITI_BROWZER_SERVICE}.ziti = brozac.ziti，it has me confused — I don’t actually have a brozac.ziti host. I understand that it uses a name for dialing, but is the .ziti suffix required? Also, how is port 80 being determined?
Glad to hear you got things sorted! How exciting! I totally understand your confusion over that intercept config...
I wrote that doc, when I made services for browser sometimes I needed to make sure the service works OUTSIDE browser first. That means, I created intercept configs just in case I needed to access them using a tunneler (for debug purposes). It can be helpful when helping myself, or forum members like yourself.
I'm pretty sure browzer doesn't use this intercept config at all, so I think you don't even need the intercept config... I'll confirm that later and follow up if I'm wrong.
As for the .ziti domain, that's just an example. One of the cool features of ziti is the private dms you get, where you're able to use fictitious domain names.
Hope that helps clear things up
@TheLumberjack Thank you for your continued assistance. I have one last question: how can I connect an HTTPS service using BrowZer? It would be great if there are any related articles or videos available. I’ve been searching the forum for relevant topics, but it’s not very efficient.