Hi, I was able to deploy VEBA and I received welcome screen with Appliance configuration and Appliance Provider Status.

However veba did not integrate with vCenter. I don't have plugin in and if I am go to https://applaince/status/vcenter I am receiving info "no healthy upstream".

I used user with more then read rights, so there should be no issue.

Maybe some service did not started, however I reboot appliance and still no joy.

Any hints, please?

What version is your vCenter Server?

If its vSphere 7.0 Update 3, you'll need to follow https://williamlam.com/2021/10/heads-up-no-healthy-upstream-error-with-veba-vsphere-ui-plugin-with-vsphere-7-0-update-3.html and apply the workaround

Thank you!

Hi, I am unable to download VEBA appliance . Error displayed page is currently down or permanently moved . KIndly , confirm on the same if any new URL to download it .

Hi Hemant,

Sorry about that, it should now be fixed

Thanks William for quick fix !!

Hey Guys,

i have trouble to acces the web ui after the deployment.

DNS Entry is set, it have an internet connection, ping etc. is working well.

Do u have any Idea where the problem could be? I disabled the tls verification within the deployment.

I deployed the openfaas veba on my vcenter. We want to use the nsx-t tag sync example for our environment.

I hope u could help me.

Greetings Oliver

Which Web UI are you referring to? Is this vSphere UI/VEBA integration or trying to access the VEBA Event Viewer UI?

In either case, you can follow the troubleshooting steps outlined https://vmweventbroker.io/kb/troubleshoot-appliance and see if that helps.

You can also enable debugging and take a look at the logs in /var/log/bootstrap-debug.log and see if anything stands out

If you're still having issues, I'd recommend joining our public Slack Channel https://vmwarecode.slack.com/archives/CQLT9B5AA to debug further

Do u have any other channel where we can try to debug? i cant join ur slack channel.

when i try to login to openfaas for deploying a function, i receive the following error:

Cannot connect to OpenFaaS on URL: https://veba01.my-domain. Get "https://veba01.my-domain/system/functions": read tcp 172.25.102.154:44816->192.168.20.31:443: read: connection reset by peer

We strongly recommend using the Knative Examples, as OpenFaaS is deprecated and will be removed in next release. We've been focusing on Knative for past several releases and there are plenty of example functions to try from. Its easier to debug in real time

Did you run through the basic troubleshooting steps mentioned above? That would be a good start to see where things are failing

Hi, I am totally new to VEBA and so I deployed version 0.6.1 several times since yesterday in our test environment. It is on the same network as the vCenter and DNS resolution is working as well as the event router. I can see the incoming events in the k8s logs. The only thing not working is accessing the endpoints in the browser or opening the OpenFaaS GUI.

A "curl -v https://[FQDN_OR_IP]" on the VEBA itself results in

OpenSSL SSL_connect: Connection reset by peer in connection to FQDN_OR_IP:443

from the vCenter it gives me

TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to FQDN_OR_IP:443
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to FQDN_OR_IP:443

We are using self signed certificates.

Currently I am running out of ideas, maybe some of you have some? ;)

Hi Jan, i have exact the same issue. Did you resolve the problem?

Curl error from the appliance: curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to xxxx

vCenter Server TLS Verification: disabled
Event Processor: Knative

p.s. is the #vcenter-event-broker-appliance channel in Slack public? How can i register?

Hi Sanjai, sorry for the late reply.

Unfortunately I wasn't successful with the VEBA until now but I was out of office for the last 2 months. I remember that I read something about a naming issue wich had affected me if I remeber correctly. The VEBA has to have the same name in the vCenter as its hostname.

You can register for the slack at this page:
https://code.vmware.com/web/code/join

When you say you're using self-signed certificates, did you change the certificates as part of the OVF properties when deploying VEBA? I suspect it has to do with your certificates, either how they were generated or they were not correctly updated within VEBA.

The team is also on community Slack if you wish to join and debug further