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
After an update to bosh v280.1.11, login to the bosh-director is not possible on using the hostname.
With calling the director API /info endpoint on using the hostname url it shows the same error: curl https://bosh-bosh.service.consul:25555/info Host not permitted
On the bosh vm itself all monit jobs are running in a healthy state and a local curl to the API
is accepted and looks fine:
After an update to bosh v280.1.11, login to the bosh-director is not possible on using the hostname.
With calling the director API
/info
endpoint on using the hostname url it shows the same error:curl https://bosh-bosh.service.consul:25555/info
Host not permitted
On the bosh vm itself all monit jobs are running in a healthy state and a local curl to the API
is accepted and looks fine:
Also calling the endpoint on using the bosh VM IP is succesful.
curl https://1.2.3.4:25555/info
Comparing to bosh v280.1.10, the behaviour with the same call on using the hostname is successful:
This issue was discussed on slack:
https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1732707019069449
Initial investigations show the cause in the Sinatra version used, which was fixed for a CVE.
The text was updated successfully, but these errors were encountered: