You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a proxy (load balancer) sitting in front of the app component which does TLS termination.
so app.baseUrl should start with https:// despite it doing http server. I thought that if app.https.certificate is not set, then it automatically assumes its http. However instead its just throwing the fact that its missing this cert.
👍 Expected behavior
if app.https.certificate is not set, don't expect it, just because baseUrl says its https.
👎 Actual Behavior with Screenshots
baseUrl dictates whether app.https.certificate should be set or not.
Hi @adminy 👋🏻 , are you using yarn start in production to run the application? This configuration is only required for local development, which is why we are asking...
📜 Description
I have a proxy (load balancer) sitting in front of the app component which does TLS termination.
so
app.baseUrl
should start withhttps://
despite it doing http server. I thought that ifapp.https.certificate
is not set, then it automatically assumes its http. However instead its just throwing the fact that its missing this cert.👍 Expected behavior
if
app.https.certificate
is not set, don't expect it, just becausebaseUrl
says its https.👎 Actual Behavior with Screenshots
baseUrl
dictates whetherapp.https.certificate
should be set or not.👟 Reproduction steps
set up demo but with
app.baseUrl
as a https link.📃 Provide the context for the Bug.
No response
🖥️ Your Environment
OS: Linux 6.12.1 - linux/x64
node: v20.16.0
yarn: 1.22.22
cli: 0.29.3-next.1 (installed)
backstage: 1.34.0-next.1
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: