Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New VM created in Azure with getbc gives SSL error #3534

Open
anwar0206 opened this issue May 7, 2024 · 2 comments
Open

New VM created in Azure with getbc gives SSL error #3534

anwar0206 opened this issue May 7, 2024 · 2 comments
Assignees

Comments

@anwar0206
Copy link

HI, Creating a new VM in Azure with https://aka.ms/getbc.
All the parameters are filled as required, When the BC Container is ready and accessed it gives SSL error whether it is accessed within the VM or from outside the VM.
User can't download the symbols also.

image
image

When trying to access the Certificate from the path, provided in the installation status page, gives below error.
image

Not sure the reason getting this error. Have created many Azure VM's with getbc script and it works.

@freddydk
Copy link
Contributor

freddydk commented May 7, 2024

I think the certificate.cer is only available when using self-signed certificates.
It looks like you are using traefik, which should handle this - but maybe this stopped working???
Travelling this week - won't be able to look at anything before next week.

@freddydk
Copy link
Contributor

Just tested this and it works fine here.
The way the certificates work are:
If you specify an email address in the field "Email for LetsEncrypt", then traefik (or I) will try to get a LetsEncrypt certificate for the VM. If that fails (for whatever reason) traefik (and I) will revert to self-signed.
I created this https://fktraefik.swedencentral.cloudapp.azure.com/bcserver - which you can see it letsencrypt:
image

and this:
https://fknotraefik.swedencentral.cloudapp.azure.com/BC - which also is letsencrypt - but created by me.

What happened in your case, I don't know - but maybe letsencrypt limits or a transient issue.

so - remove the VM and try again would probably be my best suggestion.
remember a valid email address in the letsencrypt field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants